Generating device, re-encrypting device, method, and computer program product

ABSTRACT

According to an embodiment, a generating device includes a first key generator, a second key generator, an output unit, and an update unit. The first key generator is configured to generate a first key that is a sequence of bits according to a first key rule on the basis of a random number. The second key generator is configured to generate multiple second keys that are sequences of bits partially having correlation with one another according to a second key rule on the basis of the first key. The output unit is configured to output the first key and at least one of the second keys. The update unit is configured to generate update information for updating a second key by updating a partial sequence of the second key, the partial sequence having no correlation with the other second keys not to be updated.

CROSS-REFERENCE TO RELATED APPLICATION

This application is based upon and claims the benefit of priority from Japanese Patent Application No. 2013-146888, filed on Jul. 12, 2013; the entire contents of which are incorporated herein by reference.

FIELD

Embodiments described herein relate generally to a generating device configured to generate an encryption key, a re-encrypting device, a method therefor, and a computer program product therefor.

BACKGROUND

Medical data such as personal medical histories or health information is stored for a long time to keep track of physical conditions that could possibly develop into illness in the future or to allow proper medical treatments. Any leakage of such information causes serious damage because medical information contains personal information.

The risk of information leakage increases as the retention term increases. Examples of known technologies for securely keeping information concealed for a long time include encryption technologies that information-theoretically ensure security.

When an encryption technology that information-theoretically ensures security is used, a communication device requires, for each communication counterpart, an encryption key having the same length as the plaintext to be communicated. Therefore, the size of the encryption key to be managed by the communication device is increased when there are a large number of communication counterparts or when a long plaintext is to be communicated. It is therefore desirable to reduce the entire size of multiple encryption keys stored by multiple communication counterparts and to collectively manage the encryption keys.

Furthermore, since an encryption key having the same bit length as a plaintext is required for encryption, continuous encrypted communication requires a certain number of times of encryption or updating every predetermined time period. If the entire size of multiple encryption keys is reduced and the encryption keys are collectively managed, these encryption keys have to be collectively updated. Thus, even if some of multiple encryption keys need to be updated, all of the encryption keys have to be updated.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of the configuration of an encryption system according to a first embodiment;

FIG. 2 is a schematic diagram of a relation between a server key and a plurality of client keys;

FIG. 3 is a schematic diagram of updated bit positions of client keys;

FIG. 4 is another schematic diagram of updated bit positions of client keys;

FIG. 5 is a schematic diagram of the configuration of a generating device;

FIG. 6 is a schematic diagram of the configuration of a client terminal;

FIG. 7 is a schematic diagram of the configuration of a server;

FIG. 8 is a flowchart of a process performed by the generating device;

FIG. 9 is a schematic diagram of details of a server key function;

FIG. 10 is a schematic diagram of details of a client key function;

FIG. 11 is a schematic diagram expressing details of the server key function by a function;

FIG. 12 is a schematic diagram expressing details of the client key function by functions;

FIG. 13 is a schematic diagram of the configuration of an update unit according to a first example;

FIG. 14 is a flowchart of a process performed by the update unit according to the first example;

FIG. 15 is a schematic diagram of the configurations of a client terminal and a server according to the first example;

FIG. 16 is a schematic diagram of the configuration of an update unit according to a second example;

FIG. 17 is a flowchart of a process performed by the update unit according to the second example;

FIG. 18 is a schematic diagram of the configurations of a client terminal and a server according to the second example;

FIG. 19 is a schematic diagram of the configuration of an update unit according to a third example;

FIG. 20 is a flowchart of a process performed by the update unit according to the third example;

FIG. 21 is a schematic diagram of the configurations of a client terminal and a server according to the third example;

FIG. 22 is a schematic diagram of the configuration of an update unit according to a fourth example;

FIG. 23 is a flowchart of a process performed by the update unit according to the fourth example;

FIG. 24 is a schematic diagram of the configurations of a client terminal and a server according to the fourth example;

FIG. 25 is a schematic diagram of the configuration of an update unit according to a fifth example;

FIG. 26 is a flowchart of a process performed by the update unit according to the fifth example;

FIG. 27 is a schematic diagram of the configurations of a client terminal and a server according to the fifth example;

FIG. 28 is a schematic diagram of the configuration of an encryption system according to a second embodiment;

FIG. 29 is a schematic diagram of the configuration of a re-encrypting device;

FIG. 30 is a flowchart of a process performed by the encryption system according to the second embodiment; and

FIG. 31 is a schematic diagram of a hardware configuration of a computer.

DETAILED DESCRIPTION

According to an embodiment, a generating device includes a first key generator, a second key generator, an output unit, and an update unit. The first key generator is configured to generate a first key that is a sequence of bits according to a first key rule for generating the first key on the basis of a random number. The second key generator is configured to generate multiple second keys that are sequences of bits partially having correlation with one another according to a second key rule for generating the second keys on the basis of the first key. The output unit is configured to output the first key and at least one of the second keys. The update unit is configured to generate update information for updating any one of the second keys by updating a partial sequence of the any one of the second keys, the partial sequence having no correlation with the other second keys not to be updated.

First Embodiment

FIG. 1 is a schematic diagram of the configuration of an encryption system 10 according to a first embodiment. The encryption system 10 includes a generating device 20, a plurality of client terminals 30, and a server 40.

The generating device 20 is an information processing device such as a computer. The generating device 20 generates a server key (first key) K_(S) from a random number based on a server key rule (first key rule). The generating device 20 also generates a plurality of (n, in this example) client keys (second keys) K_(i) (=K₁, K₂, . . . , K_(n)) each of which is a bit sequence partly having a correlation with one another from the server key K_(S) based on a client key rule (second key rule).

Here, n represents the number of client keys K_(i) generated from one server key K_(S), and is an integer equal to or larger than two; i is a value for identifying each of the client keys K_(i), and referred to as an index; and i is associated with each of the client keys K_(i), and is an integer equal to or larger than one and equal to or smaller than n, in this example.

Each of the n client keys K_(i) is a bit sequence for encrypting a plaintext to generate a ciphertext, and for decrypting the ciphertext into the plaintext. In other words, the client key K_(i) is an encryption key containing the same data sequence for the encryption and the decryption. Each of the n client keys K_(i) is secret information managed confidentially.

Note that each of the n client keys K_(i) may be a bit sequence that is a seed for generating an encryption key EK_(i) (=EK₁, EK₂, . . . , EK_(n)). Each of the encryption keys EK_(i) is a bit sequence for encrypting a plaintext to generate a ciphertext, and for decrypting the ciphertext into the plaintext. Thus, when the client keys K_(i) are seeds for generating the encryption keys EK_(i), the client keys K_(i) themselves do not serve as keys.

In this case, the generating device 20 generates a conversion function Fδ_(i) (=Fδ₁, Fδ₂, . . . , Fδ_(n)) in association with each of the client keys K_(i). The conversion function Fδ_(i) is a function, a program, or the like for causing a computer to convert bits. Examples of the conversion function Fδ_(i) includes a one-to-one function and a pseudo-random function.

The server key K_(S) is a bit sequence used as a seed for generating the n client keys K_(i). The data sequence of the server key K_(S) itself is not an encryption key for encrypting any plaintext. The server key K_(S) is also secret information managed confidentially.

The server key rule and the client key rule are electronic data described in a computer-executable format, and is a function, a program, or the like executed by a computer, for example. The server key rule is a rule (e.g., a function or a program) for generating a server key K_(S) from a random number. The client key rule is a rule (e.g., a function or a program) for generating client keys K_(i) from the server key K_(S).

More specifically, a client key rule is a rule for extracting one or more partial sequences from the server key K_(S) and generating client keys K_(i). In other words, a client key rule is a rule for determining a client key K_(i). A client key K_(i) is determined based on a first partial sequence set having one or more partial sequences as its elements. At least one partial sequence is shared between first partial sequence sets for two client keys K_(i), among a plurality of client keys K_(i). A partial sequence is partial information of the server key K_(S). The server key rule and the client key rule may be public information (in other words, information not concealed), or may be secret information managed confidentially.

The generating device 20 generates index information indicating association between the index i of a client key K_(i) and each of the client terminals 30. One client terminal 30 may be associated with a plurality of indices i. The generating device 20 transmits each of the n client keys K_(i) generated by the generating device 20 to a client terminal 30 associated with the index i. When the client keys K_(i) are seeds for generating the encryption keys EK_(i), the generating device 20 also transmits a conversion function Fδ_(i) associated with each of the client keys K_(i) to the client terminal 30.

The generating device 20 transmits the server key K_(S) thus generated and the client key rule to the server 40. When a public client key rule is used, the generating device 20 does not need to transmit the client key rule to the server 40. The generating device 20 also transmits the index information to the server 40. When the client keys K_(i) are seeds for generating the encryption keys EK_(i), the generating device 20 also transmits a conversion function Fδ_(i) associated with each of the indices i to the server 40.

The generating device 20 generates server key update information sri and client key update information cri for updating any of a plurality of client keys K_(i) after a predetermined number of times of encrypted communication or after a lapse of a predetermined period from generation of the server key K_(S) and the client keys K_(i). The generating device 20 transmits the server key update information sri to the server 40. The generating device 20 also transmits the client key update information cri to a client terminal 30 storing a client key K_(i) to be updated.

The server 40 is an example of an information processing device (first information processing device) configured to execute data processing. The server 40 receives the server key K_(S) and the client key rule from the generating device 20. When a public client key rule is used, the server 40 acquires the client key rule from the source information processing device. The server 40 also receives the index information indicating association between each of the client terminals 30 and the index i of the associated client key K_(i) received by that client terminal 30 from the generating device 20. When the client keys K_(i) are seeds for generating the encryption keys EK_(i), the server 40 also receives the conversion function Fδ_(i) associated with each of the indices i from the generating device 20.

The server 40 receives the server key update information sri from the generating device 20 after a predetermined number of times of encrypted communication or after a lapse of a predetermined period from reception of the server key K_(S). The server 40 updates at least one of the stored server key K_(S) and client key rule on the basis of the received server key update information sri. When the client keys K_(i) are seeds for generating the encryption keys EK_(i), the server 40 may also update the conversion function Fδ_(i) associated with client key K_(i) to be updated on the basis of the received server key update information sri.

Each of the client terminals 30 is an example of another information processing device (second information processing device) configured to execute data processing. Each of the client terminals 30 may be various types of medical equipment or electronic devices provided with a build-in information processing device. Each of the client terminals 30 receives an associated client key K_(i) from the generating device 20. When the client keys K_(i) are seeds for generating the encryption keys EK_(i), each of the client terminals 30 also receives the conversion function Fδ_(i) associated with the client key K_(i) from the generating device 20.

A client terminal 30 storing a client key K_(i) to be updated receives the client key update information cri from the generating device 20 after a predetermined number of times of encrypted communication or after a lapse of a predetermined period from reception of the client key K_(i). The client terminal 30 updates the stored client key K_(i) on the basis of the received client key update information cri. When the client keys K_(i) are seeds for generating the encryption keys EK_(i), the client terminal 30 may also update the conversion function Fδ_(i) on the basis of the received client key update information cri.

In the encryption system 10 having such a configuration, encrypted communications are established between the server 40 and each of the client terminals 30 using the client keys K_(i). When ciphertexts are to be communicated from the client terminals 30 to the server 40, the following process is performed.

Each of the client terminals 30 generates a ciphertext C_(i) (=C₁, C₂, . . . , C_(n)) by encrypting a plaintext M_(i) (=M₁, M₂, . . . , M_(n)) by using an associated client key K_(i) (=K₁, K₂, . . . , K_(n)). As an example, each of the client terminals 30 generates a ciphertext C_(i) by performing exclusive OR operation on the plaintext M_(i) and the client key K_(i) which have the same bit length as each other. Each of the client terminals 30 then transmits the ciphertext C_(i) thus generated to the server 40.

When the client keys K_(i) are seeds for generating the encryption keys EK_(i), each of the client terminals 30 generates an encryption key EK_(i) (=EK₁, EK₂, . . . , EK_(n)) from the associated client key K_(i) (=K₁, K₂, . . . , K_(n)) and the associated conversion function Fδ_(i) (=Fδ₁, Fδ₂, . . . , Fδ_(n)). Here, EK_(i)=Fδ_(i)(K_(i)) is satisfied. Each of the client terminals 30 then generates a ciphertext C_(i) (=C₁, C₂, . . . , C_(n)) by encryption using the associated encryption key EK_(i) (=EK₁, EK₂, . . . , EK_(n)).

The server 40 receives the ciphertext C_(i) from the client terminal 30. The server 40 refers to the index information and detects the index i of the client key K_(i) used in encrypting the ciphertext C_(i) from the terminal information of the client terminal 30 having transmitted the ciphertext C_(i). The server 40 inputs the detected index i and the server key K_(S) to the client key rule to generate an associated client key K_(i). The server 40 then generates the plaintext M_(i) by decrypting the ciphertext C_(i) using the client key K_(i) thus generated. When the client keys K_(i) are seeds for generating the encryption keys EK_(i), the server 40 generates an encryption key EK_(i) from the generated client key K_(i) and the associated conversion function Fδ_(i), and generates the plaintext M_(i) using the encryption key EK_(i) thus generated.

When a ciphertext is to be communicated from the server 40 to the client terminal 30, the following process is performed. The server 40 refers to the index information and detects the index i of the client key K_(i) stored by a destination client terminal 30 from the terminal information of the destination client terminal 30. The server 40 inputs the detected index i and the server key K_(S) to the client key rule to generate an associated client key K_(i). The server 40 generates the ciphertext C_(i) by encrypting the plaintext M_(i) using the client key K_(i). The server 40 then transmits the ciphertext C_(i) thus generated to the associated client terminal 30. The client terminal 30 in receipt of the ciphertext C_(i) generates the plaintext M_(i) by decrypting the ciphertext C_(i) with the client key K_(i) stored on the client terminal 30.

When the client keys K_(i) are seeds for generating the encryption keys EK_(i), the server 40 generates an encryption key EK_(i) from the generated client key K₁ and the associated conversion function Fδ_(i), and generates the ciphertext C_(i) by using the encryption key EK_(i) thus generated. The client terminal 30 in receipt of the ciphertext C_(i) generates the encryption key EK_(i) from the stored client key K_(i) and the associated conversion function Fδ_(i), and generates the plaintext M_(i) by using the encryption key EK_(i) thus generated.

For example, the encryption system 10 having such a configuration allows the server 40 to collect and to collectively manage privacy information and the like stored by a large number of client terminals 30. For example, the encryption system 10 may be applied to a medical system in which the server 40 collects detection data from a plurality of sensors or the like (thermometers, sphygmomanometers, heart rate monitors) configured to detect the conditions of patients and collectively manages such detection data by causing such sensors to function as the client terminals 30. When an output of the detection data is required, the server 40 can generate a corresponding client key K_(i) from the server key K_(S) and the client key rule, and decrypts the detection data.

As an example, the encryption system 10 may also use a different server key K_(S) and different client keys K_(i) for each given group (for each hospital, for each hospital ward, for each hospital department, or for each responsible doctor), so that the confidentiality to those external to the group can be enhanced.

FIG. 2 is a schematic diagram of a relation between a server key K_(S) and a plurality of client keys K_(i).

The generating device 20 generates a plurality of client keys K_(i) that are bit sequences partly correlated with one another on the basis of the client key rule for generating the client keys K_(i). Bit sequences correlated with one another herein mean, as an example, a relation of those having completely the same bit pattern, or those not having completely the same bit pattern but resulting in the same bit pattern when a predetermined data conversion is applied (e.g., a bitwise NOT operation, a one-to-one function, or a linear transformation).

By allowing the n client keys K_(i) to have such correlations, the encryption system 10 can generate some of the client keys K_(i) by using the same partial sequence of the server key K_(S). In this manner, the encryption system 10 can make the bit length of the server key K_(S) shorter than the total bit length of the n client keys K_(i). As a result, the encryption system 10 enables the server 40 to avoid storing all of the n client keys K_(i) or storing a server key K_(S) having the same bit length as the total bit length of the n client keys K_(i). Therefore, the n client keys K_(i) can be managed easily.

The sequence of one of the client keys K_(i) may include a plurality of partial sequences having a correlation with two or more of the other client keys K_(i). For example, the sequence of a first client key K₁ may include a partial sequence having a correlation with a second client key K₂ and another partial sequence having a correlation with a third client key K₃. In this manner, the generating device 20 can generate client keys K_(i) allowing the key length of the server key K_(S) to be reduced efficiently.

Furthermore, the sequence of one of the client keys K_(i) may include a partial sequence having a correlation with some of the other client keys K_(i) at the same time. For example, the sequence of the first client key K₁ may include a partial sequence having a correlation with both of the second client key K₂ and the third client key K₃. In this manner, the generating device 20 can generate client keys K_(i) allowing the key length of the server key K_(S) to be reduced efficiently.

Furthermore, the sequence of each of the client keys K_(i) may include a partial sequence having no correlation with the other client keys K_(i). In this manner, the generating device 20 can increase the security in the case of acquisition of any of the other client keys K_(i) by an attacker.

In the sequence of one of the client key K_(i), a longer partial sequence having no correlation with the other client keys K_(i) can enhance the tolerance against attacks and thus increase the security in the case of acquisition of any of the other client keys K_(i) by an attacker on one hand, but increase the bit length of the server key K_(S) on the other. By contrast, in the sequence of one of the client keys K_(i), a longer partial sequence having a correlation with any of the other client keys K_(i) can decrease the bit length of the server key K_(S) on one hand, but lower the tolerance against attacks and thus decrease the security in the case of acquisition of any of the other client keys K_(i) by an attacker on the other.

Therefore, the encryption system 10 may adjust the level of correlation between each of the client keys K_(i) and the other client keys K_(i) (e.g., the ratio of sequences with and without a correlation, the number of other client keys K_(i) having a correlation to the same sequence) depending on the environment in which the encryption system 10 is used, or the like. In this manner, the encryption system 10 can generate client keys K_(i) at the security level required by a user.

FIGS. 3 and 4 are schematic diagrams illustrating the server key K_(S) and updated bit positions of the client keys K_(i).

The generating device 20 can update some of the client keys K_(i) after generating the server key K_(S) and the client keys K_(i). In this case, the generating device 20 updates partial sequences of the client keys K_(i) to be updated having no correlation with the other client keys K_(i) that are not to be updated.

The generating device 20 further updates part of the sequence of the server key K_(S). Specifically, the generating device 20 updates part of the server key K_(S) corresponding to the partial sequences of the client keys K_(i) to be updated. In this case, the generating device 20 updates the server key K_(S) so that the sequences of updated client keys K_(i) are generated from the updated server key K_(S) and the client key rule.

Alternatively, the generating device 20 may update part of the client key rule. For example, the generating device 20 updates a conversion function for converting a partial sequence of a client key K₁ to be updated into the client key K₁. Similarly, in this case, the generating device 20 updates the client key rule so that the sequences of updated client keys K_(i) are generated from the updated server key K_(S) and the client key rule.

Alternatively, the generating device 20 may update both of the server key K_(S) and the client key rule.

For example, when one client key K₁ is to be updated and the other client keys K₂, K₃, and K₄ are not to be updated as illustrated in FIG. 3, the generating device 20 changes a partial sequence of the client key K₁ having no correlation with any of the other client keys K₂, K₃, and K₄. The generating device 20 also changes at least one of corresponding part of the sequence of the server key K_(S) and corresponding part of the client key rule.

For another example, when two client keys K₁ and K₂ are to be updated and the other client keys K₃ and K₄ are not to be updated as illustrated in FIG. 4, the generating device 20 changes partial sequences of the client keys K₁ and K₂ having no correlation with any of the other client keys K₃ and K₄. In this case, the generating device 20 may also change sequences having a correlation only between the client key K₁ and the client key K₂. Similarly, in this case, the generating device 20 changes at least one of corresponding part of the sequence of the server key K_(S) and corresponding part of the client key rule.

In this manner, the encryption system 10 can individually update some of the client keys K_(i) even when the client keys K_(i) have correlation among them. As a result, the encryption system 10 can efficiently update a plurality of client keys K_(i).

FIG. 5 is a schematic diagram of the configuration of the generating device 20 according to the first embodiment. The generating device 20 includes an input unit 51, a random number generator 52, a server key generator (first key generator) 53, a client key generator (second key generator) 54, an output unit 55, and an update unit 60.

The input unit 51 receives an input of a key generation request entered by a user. The input unit 51 also receives a server key rule and a client key rule from an external information processing device or the like. Alternatively, the input unit 51 may acquire the internal server key rule and the client key rule that are privately stored, without receiving the server key rule and the client key rule from an external information processing device or the like. The input unit 51 passes the server key rule to the server key generator 53, and passes the client key rule to the client key generator 54 and to the output unit 55.

The random number generator 52 generates a random number, and passes the random number thus generated to the server key generator 53. The server key generator 53 generates a server key K_(S) from the random number generated by the random number generator 52 on the basis of the server key rule received from the input unit 51. The server key generator 53 passes the server key K_(S) thus generated to the client key generator 54 and to the output unit 55.

The client key generator 54 generates the n client keys K_(i) from the server key K_(S) received from the server key generator 53 and the client key rule received from the input unit 51. The client key generator 54 passes the n client keys K_(i) thus generated to the output unit 55. When the client keys K_(i) are seeds for generating the encryption keys EK_(i), the client key generator 54 also generates n conversion functions Fδ_(i) and passes the conversion functions Fδ_(i) to the output unit 55.

The output unit 55 outputs the server key K_(S) received from the server key generator 53 and the client key rule received from the input unit 51 to the server 40. The output unit 55 does not need to output the client key rule to the server 40 when the server 40 is capable of acquiring the client key rule from an external information processing device or the like.

The output unit 55 also outputs the n client keys K_(i) received from the client key generator 54 to the respective client terminals 30. The output unit 55 also outputs index information indicating association between a client terminal 30 and the index i of the client key K_(i) output to the client terminal 30 to the server 40. When the client keys K_(i) are seeds for generating the encryption keys EK_(i), the output unit 55 also outputs each of the n conversion functions Fδ_(i) to the associated client terminal 30.

The update unit 60 inputs an update request from a user. The update unit 60 further inputs a set of indices i of the client keys K_(i) to be updated. The update unit 60 receives the server key rule and the client key rule input by the input unit 51. The update unit 60 generates server key update information sri and client key update information cri on for updating the client keys K_(i) to be updated on the basis of the server key rule and the client key rule. Note that the server key update information sri and the client key update information cri are generated on the basis of a random number, public information, a system management number, a key revision number, or the like.

The update unit 60 outputs the client key update information cri to the client terminals 30. The update unit 60 also outputs the server key update information sri to the server 40. Details of the configuration of the update unit 60 will be further described with reference to FIG. 13 and subsequent figures.

FIG. 6 is a schematic diagram of the configuration of a client terminal 30 according to the first embodiment. The client terminal 30 includes an in-client storage unit 61, an in-client converter 62, an in-client encrypter 63, an in-client transmitter 64, an in-client receiver 65, an in-client decrypter 66, and an in-client update unit 67.

The in-client storage unit 61 receives and stores the client key K_(i) output from the generating device 20. When the client keys K_(i) are seeds for generating the encryption keys EK_(i), the in-client storage unit 61 also receives and stores the conversion function Fδ_(i) output from the generating device 20.

When the client keys K_(i) are seeds for generating the encryption keys EK_(i), the in-client converter 62 converts the client key K_(i) stored by the in-client storage unit 61 into an encryption key EK_(i) on the basis of the conversion function Fδ_(i). When the client key K_(i) serves as an encryption key without any change, the client terminal 30 need not include the in-client converter 62.

When a ciphertext C_(i) is to be transmitted to the server 40, the in-client encrypter 63 receives a plaintext M_(i) from the client terminal itself, for example. The in-client encrypter 63 generates the ciphertext C_(i) by encrypting the received plaintext M_(i) by using the client key K_(i) stored by the in-client storage unit 61 or the encryption key EK_(i) resulting from conversion by the in-client converter 62. The in-client encrypter 63 then passes the ciphertext C_(i) thus generated to the in-client transmitter 64. The in-client transmitter 64 then transmits the ciphertext C_(i) received from the in-client encrypter 63 to the server 40.

When a ciphertext C_(i) is to be received from the server 40, the in-client receiver 65 receives the ciphertext C_(i) transmitted from the server 40, and passes the received ciphertext C_(i) to the in-client decrypter 66. The in-client decrypter 66 then generates a plaintext M_(i) by decrypting the ciphertext C_(i) received from the in-client receiver 65 with the client key K_(i) stored by the in-client storage unit 61 or the encryption key EK_(i) resulting from conversion by the in-client converter 62. The in-client decrypter 66 then outputs the plaintext M_(i) thus generated to the client terminal itself, for example. When the encryption and decryption are executed by the same process, the in-client encrypter 63 and the in-client decrypter 66 may be realized as one module, for example.

The in-client update unit 67 receives the client key update information cri output from the generating device 20. The in-client update unit 67 updates the client key K_(i) or the conversion function Fδ_(i) stored by the in-client storage unit 61 according to the received client key update information cri.

The in-client converter 62 may convert the client key K_(i) into the encryption key EK_(i) when the client key K_(i) and the conversion function Fδ_(i) is first received from the generating device 20 or updated by the generating device 20, instead of converting the client key K_(i) into the encryption key EK_(i) each time a ciphertext C_(i) is transmitted and received. In this case, the in-client storage unit 61 stores the encryption key EK_(i) resulting from conversion by the in-client converter 62. The in-client encrypter 63 and the in-client decrypter 66 then acquires the encryption key EK_(i) from the in-client storage unit 61 each time a ciphertext C_(i) is transmitted and received.

FIG. 7 is a schematic diagram of the configuration of the server 40 according to the first embodiment. The server 40 includes an in-server storage unit 71, an in-server receiver 72, an in-server client key generator 73, an in-server converter 74, an in-server decrypter 75, an in-server encrypter 76, an in-server transmitter 77, and an in-server update unit 78.

The in-server storage unit 71 receives and stores the server key K_(S) and the client key rule from the generating device 20. When a public client key rule is used, the in-server storage unit 71 receives the client key rule from the source information processing device. The in-server storage unit 71 also receives and stores the index information indicating a relation between each of the client terminals 30 and the index i of the client key K_(i) from the generating device 20. When the client keys K_(i) are seeds for generating the encryption keys EK_(i), the in-server storage unit 71 also receives and stores n conversion functions Fδ_(i) output from the generating device 20.

The in-server receiver 72 receives the ciphertext C_(i) transmitted by the client terminal 30, and passes the received ciphertext C_(i) to the in-server decrypter 75. The in-server receiver 72 also passes the terminal information identifying the client terminal 30 having transmitted the ciphertext C_(i) to the in-server client key generator 73.

When the ciphertext C_(i) is received, the in-server client key generator 73 identifies the index i of the client key K_(i) used in generating the ciphertext C_(i), on the basis of the terminal information received from in-server receiver 72 and the index information stored by the in-server storage unit 71. Once the index i is identified, the in-server client key generator 73 generates the client key K_(i) associated with the index i from the server key K_(S) stored by the in-server storage unit 71 on the basis of the client key rule also stored by the in-server storage unit 71.

When the client keys K_(i) are seeds for generating the encryption keys EK_(i), the in-server converter 74 receives the client key K_(i) generated by the in-server client key generator 73. The in-server converter 74 converts the received client key K_(i) into the encryption key EK_(i) on the basis of the associated conversion function Fδ_(i) stored by the in-server storage unit 71. When the client key K_(i) serves as an encryption key without any change, the server 40 need not include the in-server converter 74. Alternatively, the server 40 may include a block combining the in-server client key generator 73 and the in-server converter 74. In this case, the combination block executes a combined function combining the client key rule and the conversion function to directly generate an encryption key EK_(i) from an index i.

The in-server decrypter 75 generates a plaintext M_(i) by decrypting the ciphertext C_(i) received from the in-server receiver 72 by using the client key K_(i) generated by the in-server client key generator 73 or the encryption key EK_(i) resulting from conversion by the in-server converter 74. The in-server decrypter 75 then outputs the plaintext M_(i) thus generated.

When a ciphertext C_(i) is to be transmitted, the in-server client key generator 73 acquires the terminal information identifying the destination client terminal 30 to which the ciphertext is to be transmitted. The in-server client key generator 73 identifies the index i of the client key K_(i) stored on the destination client terminal 30 on the basis of the received terminal information and the index information stored by the in-server storage unit 71. Once the index i is identified, the in-server client key generator 73 generates the client key K_(i) associated with the index i from the server key K_(S) stored by the in-server storage unit 71 on the basis of the client key rule also stored by the in-server storage unit 71.

When the client keys K_(i) are seeds for generating the encryption keys EK_(i), the in-server converter 74 receives the client key K_(i) generated by the in-server client key generator 73. The in-server converter 74 converts the received client key K_(i) into the encryption key EK_(i) on the basis of the associated conversion function Fδ_(i) stored by the in-server storage unit 71.

The in-server encrypter 76 receives a plaintext M_(i) from the external. The in-server encrypter 76 generates the ciphertext C_(i) by encrypting the plaintext M_(i) thus received with the client key K_(i) received from the in-server client key generator 73 or the encryption key EK_(i) resulting from conversion by the in-server converter 74. The in-server encrypter 76 then passes the ciphertext C_(i) thus generated to the in-server transmitter 77. The in-server transmitter 77 then transmits the ciphertext C_(i) received from the in-server encrypter 76 to the destination client terminal 30. When the encryption and decryption are executed by the same process, the in-server decrypter 75 and the in-server encrypter 76 may be realized as one module, for example.

FIG. 8 is a flowchart of a process performed by the generating device 20 according to the first embodiment. To begin with, at Step S11, the input unit 51 in the generating device 20 receives a key generation request. Subsequently, at Step S12, the input unit 51 acquires a server key rule and a client key rule. At Step S12, the input unit 51 may also acquire a conversion function Fδ_(i) for converting a bit sequence of a client key K_(i) into a bit sequence of an encryption key EK_(i).

Subsequently, at Step S13, the server key generator 53 in the generating device 20 executes the server key rule to generate a server key K_(S) based on a random number. In this example, the server key rule is a server key function that receives an input of a random number r and outputs a bit sequence of a server key K_(S), as indicated in Expression (1) below. The server key function indicated in Expression (1) will be described later in detail with reference to FIG. 9.

SKeyGen(r)→K _(s)  (1)

The client key generator 54 in the generating device 20 then executes a loop process from Step S14 to Step S17 for each of the indices i. In this example, the client key generator 54 executes the process at Step S15 and Step S16 while incrementing i from i=1 to i=n.

At Step S15, the client key generator 54 generates a client key K_(i) associated with the index i by executing the client key rule on the basis of the server key K_(S). In this example, the client key rule is a client key function that receives an input of the server key K_(S) and the index i, and outputs a bit sequence of the client key K_(i), as indicated by Expression (2) below. The client key function indicated in Expression (2) will be described later in detail with reference to FIG. 10.

CKeyGen(K _(s) ,i)→K _(i)  (2)

Subsequently, at Step S16, the client key generator 54 generates a conversion function Fδ_(i) for converting the bit sequence of the client key K_(i) into the encryption key EK_(i). The client key generator 54 executes Step S16 when the client key K_(i) is a seed for generating the encryption key EK_(i), but does not execute Step S16 when the bit sequence of the client key K_(i) serves as the encryption key without any change. The client key generator 54 does not execute Step S16, either, when the conversion function Fδ_(i) is already acquired at Step S12.

When i=n at Step S17, the client key generator 54 exits the loop process, and moves the process to Step S18. At Step S18, the output unit 55 in the generating device 20 outputs the server key K_(S) and the client key rule to the server 40. When the server 40 can acquire the client key rule from the external, the output unit 55 does not need to output the client key rule to the server 40. When the client keys K_(i) are seeds for generating the encryption keys EK_(i), the output unit 55 also outputs n conversion functions Fδ_(i) to the server 40.

The output unit 55 then outputs each of the n client keys K_(i) to the associated client terminal 30. When the client keys K_(i) are seeds for generating the encryption keys EK_(i), the output unit 55 also outputs each of the n conversion functions Fδ_(i) to the associated client terminal 30. Once the process at Step S18 is completed, the generating device 20 ends the process.

FIG. 9 is a schematic diagram of an example of details of the server key function (SKeyGen(r)). The server key function receives an input of a random number r.

The server key function divides the received random number r into a plurality of partial sequences. The server key function also associates multiple sets D with the partial sequences, respectively.

Each of the sets D is a set having indices as its elements, and represents every combination of the indices from 1 to n. For example, when n=3 (in other words, when i=1, 2, 3), sets D={1}, {2}, {3}, {1, 2}, {1, 3}, {2, 3}, and {1, 2, 3}. {x, y, z} represents a set of a combination of x, y, and z.

A partial sequence associated with a set D is represented by K^(D). The random number r can thus be expressed by following Expression (3), as an example. Here, ∥ is an operator for concatenating the bit sequences adjacent thereto. A partial sequence K^(D) indicates that the partial sequence is information to be used in generating client keys K_(i) corresponding to the elements of the set D. For example, K^({1,2}) is information used in generating client keys K₁ and K₂.

K ^({1}) ∥K ^({2}) ∥ . . . ∥K ^({1,2}) ∥K ^({1,3}) ∥ . . . ∥K ^({1,2,3}) ∥ . . . ∥K ^({1,2, . . . ,n}) =r  (3)

The bit length of each of the partial sequences is determined by the server key function. The bit length of a partial sequence K^(D) is represented by l^(D). l^(D) is an integer equal to or larger than zero.

The server key function arranges and concatenates a plurality of partial sequences K^(D) into a row. As an example, the server key function positions the partial sequences associated with sets D having smaller numbers of indices (elements) on the left. When the numbers of indices (elements) are the same, a partial sequence with a set D including an index (element) of a smaller value is positioned on the left.

As an example, when K^({1}) and K^({2,3}) are given, the server key function positions K^({1}), which has a smaller number of indices (elements), on the left. As another example, when K^({1,2}) and K^({2,3}) are given, the server key function positions K^({1,2}) having indices (elements) of smaller values on the left. As still another example, when K^({1,2}) and K^({1,3}) are given, the server key function positions K^({1,2}) having indices (elements) of smaller values on the left.

The server key function then concatenates the partial sequences thus arranged, and outputs a server key K_(S), as indicated in Expression (4) below. Illustrated in FIG. 9 is an exemplary arrangement for a case in which n=3.

K _(s) =K ^({1}) ∥K ^({2}) ∥ . . . ∥K ^({1,2}) ∥K ^({1,3}) ∥ . . . ∥K ^({1,2,3}) ∥ . . . ∥K ^({1,2, . . . ,n})  (4)

Such a server key function can generate an l_(S)-bit server key K_(S) from an l_(r)-bit random number, where l_(r)=l_(S), for example. The partial sequences may be arranged in any predetermined way.

FIG. 10 is a schematic diagram of an example of details of a client key function (CKeyGen(K_(S), i)). The client key function receives inputs of the server key K_(S) and a value of the index i.

The client key function extracts a plurality of partial sequences K^(D) from the server key K_(S) thus received. In other words, the client key function extracts the partial sequences in the manner indicated by Expression (5) below. In FIG. 10, (a) indicates the partial sequences extracted when n=3.

K ^({1}) ,K ^({2}) , . . . K ^({1,2}) ,K ^({1,3}) , . . . K ^({1,2,3}) , . . . K ^({1,2, . . . ,n})  (5)

The client key function then selects two or more partial sequences associated with the sets including the index value thus received as its element from the partial sequences thus extracted. For example, when i=1, the client key function selects partial sequences indicated by Expression (6) below. In FIG. 10, (b) indicates partial sequences selected when n=3, i=1.

K ^({1}) ,K ^({1,2}) ,K ^({1,3}) , . . . K ^({1,2,3}) , . . . K ^({1,2, . . . ,n})  (6)

As another example, when i=2, the client key function selects the partial sequences indicated by Expression (7) below. In FIG. 10, (c) indicates the partial sequence selected when n=3, i=2.

K ^({2}) ,K ^({1,2}) ,K ^({2,3}) , . . . K ^({1,2,3}) , . . . K ^({1,2, . . . ,n})  (7)

As still another example, the client key function selects the partial sequences indicated by Expression (8) below when i=n. In FIG. 10, (d) indicates the partial sequence selected when n=3, i=3.

K ^({n}) ,K ^({1,n}) ,K ^({2,n}) , . . . K ^({1,2,n}) , . . . K ^({1,2, . . . ,n})  (8)

The client key function then arranges and concatenates the two or more partial sequences K^(D) thus selected into a row. As an example, the client key function positions the partial sequences associated with sets D having smaller numbers of indices (elements) on the left. When the numbers of indices (elements) are the same, a partial sequence with a set D including an element of a smaller value is positioned on the left. The way at which the partial sequences are arranged is the same as that accomplished by the server key function.

The client key function then concatenates the partial sequences thus arranged, and outputs the client key K_(i). For example, when i=1, the client key function outputs the client key K₁ indicated by Expression (9) below. In FIG. 10, (e) indicates a client key K₁ output when n=3, i=1.

K ₁ =K ^({1}) ∥K ^({1,2}) ∥K ^({1,3}) ∥ . . . ∥K ^({1,2,3}) ∥ . . . ∥K ^({1,2, . . . ,n})  (9)

As another example, when i=2, the client key function outputs the client key K₂ indicated by Expression (10) below. In FIG. 10, (f) indicates the client key K₂ output when n=3, i=2.

K ₂ =K ^({2}) ∥K ^({1,2}) ∥K ^({2,3}) ∥ . . . ∥K ^({1,2,3}) ∥ . . . ∥K ^({1,2, . . . ,n})  (10)

As still another example, when i=n, the client key function outputs a client key K_(n) as indicated by Expression (11) below. In FIG. 10, (g) indicates a client key K₃ output when n=3, i=3.

K _(n) =K ^({n}) ∥K ^({1,n}) ∥K ^({2,n}) ∥ . . . ∥K ^({1,2,n}) ∥ . . . ∥K ^({1,2, . . . ,n})  (11)

The partial sequences may be arranged in any predetermined way.

In the client key K_(i) thus generated, a partial sequence associated with a set D of two or more indices (elements) has a correlation with the other client keys K_(i). In this manner, the generating device 20 according to the first embodiment can keep the total bit length of the n client keys K_(i) shorter than the bit length l_(s) of the server key K_(S) by using such a client key function as a client key rule.

FIG. 11 is a schematic diagram expressing details of the server key function by a function. The server key function is not limited to the function described with reference to FIG. 9 but may be a function that generates a server key K_(S) by performing data conversion (first data conversion Fα) on a random number r.

For example, the first data conversion Fα may be a function that outputs a random number r without any change as the server key K_(S), as indicated by Expression (21) below.

K _(s) =r  (21)

As another example, the first data conversion Fα may output a sequence resulting from converting the random number r with a function F₁, as indicated by Expression (22) below. As an example, F₁ is a one-to-one function, a pseudo-random function, or a hash function. F₁ outputs l_(S) bits (l_(r)≧l_(S)) for an input of l_(r) bits.

K _(s) =F ₁(r)  (22)

As still another example, the first data conversion Fα may output a result of an exclusive OR performed on the random number r and a sequence resulting from converting the random number r with a function F₂, as indicated by Expression (23) below. As an example, F₂ is a one-to-one function, a pseudo-random function, a hash function, or a constant function. F₂ outputs l_(S) bits for an input of l_(S) bits.

K _(s) =r⊕F ₂(r)  (23)

As another example, the first data conversion Fα may output a result of an exclusive OR performed on a sequence resulting from converting the random number r with a function F₁ and a sequence resulting from converting the random number r with a function F₃, as indicated by Expression (24) below. As an example, F₃ is a one-to-one function, a pseudo-random function, a hash function, or a constant function. F₃ outputs l_(S) bits (l_(r)≧l_(S)) for an input of l_(r) bits.

K _(s) =F ₁(r)⊕F ₃(r)  (24)

FIG. 12 is a schematic diagram expressing details of the server key function by functions. The client key function may also be a function that applies data conversion (second data conversion Fβ) to the sequence of the server key K_(S), and generates a plurality of client keys K_(i) from the sequence of a server key K_(S)′ resulting from the conversion.

For example, the second data conversion Fβ may be a function that outputs the server key K_(S) without any change as the converted server key K_(S)′, as indicated by Expression (31) below.

K _(s) ′=K _(s)  (31)

As another example, the second data conversion Fβ may also output a sequence resulting from converting the server key K_(S) with a function F₄, as the converted server key K_(S)′, as indicated by Expression (32) below. As an example, F₄ is a one-to-one function, a pseudo-random function, or a hash function. F₄ outputs l_(S) bits for an input of l_(S) bits.

K _(s) ′=F ₄(K _(s))  (32)

As another example, the second data conversion Fβ may output a result of an exclusive OR performed on the server key K_(S) and a sequence resulting from converting the server key K_(S) with a function F₅ as the converted server key K_(S)′, as indicated by Expression (33) below. As an example, F₅ is a one-to-one function, a pseudo-random function, a hash function, or a constant function. F₅ outputs l_(S) bits for an input of l_(S) bits.

K _(s) ′=K _(s) ⊕F ₅(K _(s))  (33)

As another example, the second data conversion Fβ may output a result of an exclusive OR performed on a sequence resulting from converting the server key K_(S) with a function F₄ and another sequence resulting from converting the server key K_(S) with a function F₅ as the converted server key K_(S)′, as indicated by Expression (34) below.

K _(s) ′=F ₄(K _(s))⊕F ₅(K _(s))  (34)

The client key function may also be a function that generates a client key K_(i) by applying a data conversion (third data conversion Fγ) to a sequence obtained by arranging the partial sequences K^(D) selected from the sequence of the converted server key K_(S)′ into a row (client key K_(i)′ before conversion).

For example, the third data conversion Fγ may be a function that outputs the client key K_(i)′ before conversion without any change as the client key K_(i), as indicated by Expression (41) below.

K _(i) =K _(i)′  (41)

As another example, the third data conversion Fγ may output a sequence resulting from converting the client key K_(i)′ before conversion with a function F₆ as the client key K_(i), as indicated by Expression (42) below. As an example, F₆ is a one-to-one function, a pseudo-random function, or a hash function. F₆ outputs l_(i) bits for an input of l_(i) bits.

K _(i) =F ₆(K _(i)′)  (42)

F₆ may also assume K_(i)′ as a row vector, and multiply K_(i)′ by an invertible matrix R from the right, as indicated by Expression (43) below. For example, F₆ performs the calculation assuming one bit of K_(i)′ as an element of a vector and R as an invertible matrix l_(i)×l_(i). As another example, a number represented by a plurality of bits in K_(i)′ may be assumed as an element of a vector. R may be handled as public information. By multiplying the client key K_(i)′ before conversion by the invertible matrix R, the positions of bits in a common partial sequence can be changed among the client keys K_(i) including a common partial sequence. In this manner, even when an attacker acquires the client key K_(i), it is impossible for the attacker to guess the position of the bits included in the common partial sequence in the bit sequence of a client key K_(j) sharing the common partial sequence with the client key K_(i).

F ₆(K _(i)′)=K _(i) ′×R  (43)

As another example, the third data conversion Fγ may output a result of an exclusive OR performed on the client key K_(i)′ before conversion and a sequence resulting from converting the client key K_(i)′ before conversion with a function F₇ as the client key K_(i), as indicated by Expression (44) below. As an example, F₇ is a one-to-one function, a pseudo-random function, a hash function, or a constant function. F₇ outputs l_(i) bits for an input of l_(i) bits.

K _(i) =K _(i) ′⊕F ₇(K _(i)′)  (44)

As another example, the third data conversion Fγ may also output a result of an exclusive OR performed on a sequence resulting from converting the client key K_(i)′ before conversion with the function F₆ and a sequence resulting from converting the client key K_(i)′ before conversion with the function F₇ as the client key K_(i), as indicated by Expression (45) below.

K=F ₆(K _(i)′)⊕F ₇(K _(i)′)  (45)

As another example, the third data conversion Fγ may also output a sequence resulting from converting the client key K_(i)′ before conversion and the set D with a function F₈ as the client key K_(i), as indicated by Expression (46) below. F₈ deletes a partial sequence K^(D) corresponding to the set D from K_(i)′.

K _(i) =F ₈(K _(i) ′,D)  (46)

As another example, the third data conversion Fγ may also output a plurality of sequences resulting from converting the client key K_(i)′ before conversion with a function F₉ as a plurality of client keys K_(i), K_(j), as indicated by Expression (47) below. K_(j) represents a client key that is different from K_(i). As an example, F₉ is a one-to-one function, a pseudo-random function, or a hash function.

k _(i) ∥k _(j) =F ₉(K _(i) ′,K _(j)′)  (47)

F₉ may also assume a plurality of client keys K_(i)′ as one row vector, and multiply K_(i)′ by an invertible matrix R from the right, as indicated by Expression (48) below. Expressions (47) and (48) represent an example in which there are two client keys K_(i)′ before conversion, but there may be three or more client keys K_(i)′ before conversion.

F ₉(K _(i) ′,K _(j))=[K _(i) ′,K _(j) ′]×R  (48)

Furthermore, the client key function CKeyGen(r) may be a function for collectively executing the second data conversion Fβ, the selection of partial sequences, the arrangement, and the third data conversion Fγ.

Furthermore, the generating device 20 may generate a combined function CEKGen(K_(S), i) obtained by combining the client key function CKeyGen(K_(S), i) and the conversion function Fδ_(i). In this case, the generating device 20 transmits the generated combined function CEKGen(K_(S), i) to the server 40 to allow the server 40 to directly generate the encryption key EK_(i) from the server key K_(S) and an index i.

FIG. 13 is a schematic diagram of the configuration of the update unit 60 with a client terminal 30 and the server 40 according to a first example.

In the first example, the client key K₁ is seed information for generating an encryption key EK_(i). Thus, in the first example, the generating device 20 generates a conversion function Fδ_(i) for converting each of the client keys K_(i) into an encryption key EK_(i). In the first example, the generating device 20 outputs an associated conversion function Fδ_(i) to each of the client terminals 30. In the first example, the update unit 60 updates the conversion functions Fδ_(i).

In the first example, the update unit 60 includes an input unit 80, a random number generator 81, an update information generator 82, and an output unit 83 as illustrated in FIG. 13.

The input unit 80 receives as input a set of indices i for specifying the client keys K_(i) to be updated. The set of indices i may contain only one index i or may contain a plurality of indices i. The random number generator 81 generates a random number of a predetermined number of digits.

The update information generator 82 generates a master key g_(i) associated with each of the indices i input by the input unit 80 on the basis of the random number generated by the random number generator 81. The master key g_(i) is information that is a seed for generating a conversion function Fδ_(i) associated with an index i.

The output unit 83 outputs the index i and the master key g_(i) as server key update information sri to the server 40. The output unit 83 also outputs, for each of the client terminals 30 storing the client keys K_(i) to be updated, an associated index i and the master key g_(i) as client key update information cri.

Alternatively, the update information generator 82 may generate a conversion function Fδ_(i) associated with an index i instead of the master key g_(i). In this case, the output unit 83 outputs the associated conversion function Fδ_(i) as the server key update information sri to the server 40 instead of the master key g_(i). Furthermore, in this case, the output unit 83 outputs the associated conversion function Fδ_(i) as the client key update information cri to the client terminal 30 instead of the master key g_(i).

Examples of the conversion functions Fδ_(i) include the following. The update information generator 82 may generate the conversion functions Fδ_(i) on the basis of information such as a system management number and a revision number in addition to the master key g_(i). Here, information other than the master key g_(i) will be referred to as management information w. The management information w may be either secret information or public information.

For example, the conversion function Fδ_(i) may be a function that outputs an arithmetic sum, an arithmetic product, or an exclusive OR of the client key K_(i) and the master key g_(i) as indicated by Expressions (60) to (62) below. Expression (62) is an expression when K_(i) and g_(i) have the same bit length.

Fδ _(i)(K _(i))=K _(i) +g _(i)  (60)

Fδ _(i)(K _(i))=K _(i) ×g _(i)  (61)

Fδ _(i)(K _(i))=K _(i) ⊕g _(i)  (62)

For another example, the conversion function Fδ_(i) may be a function that outputs a result of operation on the client key K_(i), the master key g_(i), and the management information w as indicated by Expression (63) below. Here, symbol ∘ represents an operator such as arithmetic addition, arithmetic multiplication, or exclusive OR operation, which also applies to other Expressions.

Fδ _(i)(K _(i))=K _(i) ∘g _(i) ∘w  (63)

For another example, the conversion function Fδ_(i) may be a function that outputs a sequence obtained by converting the sum, the product, or the exclusive OR of the client key the master key g_(i), and the management information w with a K_(i), function F₁₀ as indicated by Expression (64) below. As an example, F₁₀ is a one-to-one function, a pseudo-random function, or a hash function. F₁₀ outputs l_(i) bits for an input of l_(i) bits.

Fδ _(i)(K _(i))=F ₁₀(K _(i) ∘g _(i) ∘w)  (64)

For another example, the conversion function Fδ_(i) may assume K_(i) as a row vector and multiply K_(i) by an invertible matrix g_(i) from the right as indicated by Expression (65) below. For example, the conversion function Fδ_(z) performs the calculation assuming one bit of K_(i) as an element of a vector and a row vector of 1×l_(i), and g_(i) as an invertible matrix l_(i)×l_(i). Alternatively, for example, the conversion function Fδ_(z) may perform calculation assuming that a number represented by a plurality of bits in K_(i) as an element of a vector.

Fδ _(i)(K _(i))=K _(i) ×g _(i)  (65)

For another example, the conversion function Fδ_(i) may assume K_(i) as a column vector and add the product of a matrix w and the column vector g_(i) as indicated by Expression (66) below. For example, the conversion function Fδ_(z) performs the calculation assuming one bit of K_(i) as an element of a vector and a column vector of l_(i)×1, w as a matrix of l_(i)×l_(g), and g_(i) as a column vector of l_(g)×1. Alternatively, for example, the conversion function Fδ_(z) may perform calculation assuming that a number represented by a plurality of bits in K_(i), g_(i), and w as an element of a vector.

Fδ _(i)(K _(i))=K _(i) +w×g _(i)  (66)

For another example, the conversion function Fδ_(i) may output a result of operation of a sequence obtained by converting the client key K_(i) with a function F₁₀ and a sequence obtained by converting the master key g_(i) by a function F₁₁, as indicated by Expression (67) below. As an example, F₁₁ is a one-to-one function, a pseudo-random function, or a hash function.

Fδ _(i)(K _(i))=F ₁₀(K _(i))∘F ₁₁(g _(i))  (67)

The conversion function Fδ_(i) is not limited to such functions, but may be any function for converting the client key K_(i) with the master key g_(i), the management information w, or the like.

FIG. 14 is a flowchart of a process performed by the update unit 60 according to the first example. To begin with, at Step S111, the input unit 80 in the update unit 60 receives as input a set of indices i for specifying the client keys K_(i) to be updated. Subsequently, at Step S112, the update information generator 82 generates a master key g_(i) associated with each of the indices i input by the input unit 80 on the basis of a random number.

At Step S113, the output unit 83 then outputs the index i and the master key g_(i) to the server 40. The output unit 83 also outputs, to the client terminals 30 storing the client key K_(i) to be updated, the associated index i and the master key g_(i).

FIG. 15 is a schematic diagram of partial configurations of a client terminal 30 and the server 40 with the update unit 60 according to the first example.

In the first example, the in-client update unit 67 of the client terminal 30 to be updated acquires an index i and the master key g_(i) from the update unit 60. The in-client update unit 67 inputs the acquired index i and master key g_(i) to a pre-stored master function Gf(g_(i), i) to generate a conversion function Fδ_(i). The master function Gf(g_(i), i) is a function for generating a conversion function Fδ_(i) from the master key g_(i) and an index i. The master function Gf(g_(i), i) may be public information or may be secret information generated by the generating device 20. The master function may also be Gf(g_(i), i, w) using the management information w as an argument. The conversion function Fδ_(i) output from the master function is a function indicated by Expressions (60) to (67), for example.

The in-client update unit 67 then replaces the conversion function Fδ_(i) stored in the in-client storage unit 61 with the newly generated conversion function Fδ_(i). Alternatively, the in-client update unit 67 may acquire the conversion function Fδ_(i) instead of the master key g_(i) from the update unit 60. In this case, the in-client update unit 67 replaces the conversion function Fδ_(i) stored in the in-client storage unit 61 with the acquired conversion function Fδ_(i).

In encryption and decryption, the in-client converter 62 generates a new encryption key EK_(i) on the basis of the existing client key K_(i) stored in the in-client storage unit 61 and the new conversion function Fδ_(i). In this manner, the client terminal 30 can conduct encrypted communication with the server 40 by using the new encryption key EK_(i).

In the first example, the in-server update unit 78 in the server 40 acquires an index i and the master key g_(i) from the update unit 60. The in-server update unit 78 inputs the acquired index i and master key g_(i) to the master function Gf(g_(i), i) to generate a conversion function Fδ_(i). The master function Gf(g_(i), i) is the same as that stored in the associated client terminal 30.

The in-server update unit 78 then replaces the conversion function Fδ_(i) stored in the in-server storage unit 71 with the newly generated conversion function Fδ_(i). Alternatively, the in-server update unit 78 may acquire the conversion function Fδ_(i) instead of the master key g_(i) from the update unit 60. In this case, the in-server update unit 78 replaces the conversion function Fδ_(i) stored in the in-server storage unit 71 with the acquired conversion function Fδ_(i).

In encryption and decryption, the in-server client key generator 73 generates a client key K_(i) on the basis of an index i, the existing client key function CKeyGen(K_(S), i) and the existing server key K_(S) stored in the in-server storage unit 71. The in-server converter 74 generates a new encryption key EK_(i) on the basis of the generated client key K_(i) and the new conversion function Fδ_(i). In this manner, the server 40 can conduct encrypted communication with the client terminals 30 by using the new encryption keys EK_(i).

According to the update unit 60 according to the first example, the encryption key EK_(i) can be updated by updating the conversion function Fδ_(i).

FIG. 16 is a schematic diagram of the configuration of the update unit 60 with a client terminal 30 and the server 40 according to a second example. In description of the second example, components having substantially the same configuration and functions as those in the first example will be designated by the same reference numerals and the description thereof will not be repeated except for differences.

In the second example, the generating device 20 updates the client keys K_(i) to be updated. In addition, the generating device 20 updates some bits of the server key K_(S). Specifically, the generating device 20 updates bits of the server key K_(S) that are a seed for the client keys K_(i) to be updated but are not a seed for the client keys K_(i) not to be updated.

In the second example, the update unit 60 includes an input unit 80, a random number generator 81, a first update information generator 84, a second update information generator 85, and an output unit 83 as illustrated in FIG. 16.

The first update information generator 84 generates server key update information sri. The first update information generator 84 includes a position detector 91 and a value generator 92.

The position detector 91 detects a bit position (update position P) of the server key K_(S) that is a seed for the client keys K_(i) to be updated but is not a seed for the client keys K_(i) not to be updated on the basis of each of the indices input by the input unit 80. Specifically, the position detector 91 detects such bit positions that a change in the bit values at the positions will result in a change in the client keys K_(i) to be updated but will not result in a change in the client keys K_(i) not to be updated.

For example, when the client key function CKeyGen(K_(S), i) executes conversion as illustrated in FIG. 10, the bit position of the partial sequence in the server key K_(S) is known in advance. Thus, for the conversion illustrated in FIG. 10, the position detector 91 detects a bit position (update position P) that is a seed for the client keys K_(i) to be updated but is not a seed for the client keys K_(i) not to be updated on the basis of the known information.

For another example, when the client key function (K_(S), i) executes the conversion illustrated in FIG. 12, the position detector 91 detects such a bit position by reversely tracking the client key function CKeyGen(K_(S), i). An example of the reverse tracking will be described below. In FIG. 12, the converted server key K_(S)′ associated with the client key K_(i)′ before conversion is known because the selection of a partial sequence and the arrangement are defined. The position detector 91 thus detects a bit position of the server key K_(S) before conversion that can be updated on the basis of association between the converted server key K_(S)′ and the server key K_(S) before conversion.

The second example can be applied when the second data conversion Fβ is replacement or linear conversion. Thus, a case in which K_(S)′=Fβ (K_(S))=φ(K_(S)) is satisfied is assumed. φ is a matrix representing replacement or linear conversion. B is a set of bit positions of K_(S)′ to be updated. A position of a column where the bεB-th row is 1 is assumed to be an update position P. This cannot be applied when a column with a row containing b and a row not containing b are both 1 is included in the matrix φ.

Specific details are described below. K_(S)′ and K_(S) are assumed to be as follows. Both of x_(i) and y_(i) are one bit.

${K_{s}^{\prime} = \begin{bmatrix} y_{1} \\ y_{2} \\ y_{3} \\ y_{4} \\ y_{5} \end{bmatrix}},{K_{s} = {{\begin{bmatrix} x_{1} \\ x_{2} \\ x_{3} \\ x_{4} \\ x_{5} \end{bmatrix}\begin{bmatrix} y_{1} \\ y_{2} \\ y_{3} \\ y_{4} \\ y_{5} \end{bmatrix}} = {\begin{bmatrix} 0 & 1 & 0 & 0 & 1 \\ 0 & 0 & 1 & 1 & 0 \\ 1 & 0 & 0 & 0 & 1 \\ 0 & 0 & 0 & 1 & 0 \\ 0 & 0 & 1 & 0 & 0 \end{bmatrix}\begin{bmatrix} x_{1} \\ x_{2} \\ x_{3} \\ x_{4} \\ x_{5} \end{bmatrix}}}}$

When values to be updated in K_(S)′ are x₁ and y₃, the bit positions to be updated are the first bit and the third bit. Thus, the set of bit positions to be updated in K_(S)′ is B={1,3}. Columns where the first (b=1) row is 1 are the second and the fifth columns. Columns where the third (b=3) row is 1 are the first and the fifth columns. Thus, in this specific example, the update positions P in the server key K_(S) before conversion are P=1, 2, 5.

Since the bit positions are reversely tracked for detection, the client key function CKeyGen(K_(S), i) needs to be a function for changing or linearly converting the bit positions in the second example. Therefore, in the second example, the client key function CKeyGen(K_(S), i) is not a pseudo random function, a hash function and the like that cannot reversely track the bit positions.

The position detector 91 further generates information indicating the number l of total bits of the detected bit positions.

The value generator 92 generates an update value V of the number l of bits generated by the position detector 91 on the basis of a random number generated by the random number generator 81.

The second update information generator 85 generates client key update information cri. The second update information generator 85 includes a server key generator 93, and a client key generator 94.

The server key generator 93 generates a new server key K_(S) resulting from update on the basis of the server key K_(S) before update, the update positions P, and the update value V. Specifically, the server key generator 93 replaces the values at the bit positions represented by the update positions P in the server key K_(S) before update with the values represented by the update values V. The client key generator 94 generates a new client key K_(i) on the basis of the index i input by the input unit 80, the existing client key function CKeyGen(K_(S), i) and the new server key K_(S) resulting from the update.

The output unit 83 outputs the update positions P and the update value V generated by the first update information generator 84 to the server 40. The output unit 83 also outputs, for each of the client terminals 30 storing the client keys K_(i) to be updated, the new client key K_(i) generated by the second update information generator 85.

FIG. 17 is a flowchart of a process performed by the update unit 60 according to the second example. To begin with, at Step S121, the input unit 80 in the update unit 60 receives as input a set of indices i for specifying the client keys K_(i) to be updated.

Subsequently, at Step S122, the first update information generator 84 detects a bit position (update position P) and the number l of bit of the server key K_(S) that is a seed for the client keys K_(i) to be updated but is not a seed for the client keys K_(i) not to be updated on the basis of each of the indices i input by the input unit 80. Subsequently, at Step S123, the first update information generator 84 generates the update value V of the number l of bits on the basis of a random number.

Subsequently, at Step S124, the second update information generator 85 generate the new server key K_(S) resulting from update on the basis of the update positions P, the update value V, and the server key K_(S) before update. Subsequently, at Step S125, the second update information generator 85 generates a new client key K_(i) on the basis of the index i input by the input unit 80, the new server key K_(S) resulting from the update, and the existing client key function CKeyGen(K_(S), i).

At Step S126, the output unit 83 then outputs the update positions P and the update value V to the server 40. The output unit 83 also outputs, for each of the client terminals 30 storing the client keys K_(i) to be updated, the new client key K_(i).

FIG. 18 is a schematic diagram of partial configurations of the client terminal 30 and the server 40 with the update unit 60 according to the second example. In the second example, the in-client update unit 67 in the client terminal 30 to be updated acquires a client key K_(i) from the update unit 60. The in-client update unit 67 then replaces the client key K_(i) stored in the in-client storage unit 61 with the acquired new client key K_(i).

In this manner, the client terminal 30 can conduct encrypted communication with the server 40 by using the new client key K_(i) stored in the in-client storage unit 61 in encryption and decryption.

When the client keys K_(i) are seeds for generating the encryption keys EK_(i), the in-client converter 62 generates a new encryption key EK_(i) on the basis of the new client key K_(i) stored by the in-client storage unit 61 and the existing conversion function Fδ_(i). In this manner, the client terminal 30 can conduct encrypted communication with the server 40 by using the new encryption key EK_(i).

In the second example, the in-server update unit 78 in the server 40 acquires the update positions P and the update value V from the update unit 60. The in-server update unit 78 generates a new server key K_(S) resulting from update on the basis of the existing server key K_(S) before update, the update positions P, and the update value V. Specifically, the in-server update unit 78 replaces the values at the bit positions represented by the update positions P in the server key K_(S) before update with the values represented by the update values V. The in-server update unit 78 then replaces the existing server key K_(S) stored in the in-server storage unit 71 with the new server key K_(S) resulting from the update.

In encryption and decryption, the in-server client key generator 73 generates a new client key K_(i) on the basis of an index i, the existing client key function CKeyGen(K_(S), i) stored by the in-server storage unit 71 and the new server key K_(S) resulting from the update. In this manner, the server 40 can conduct encrypted communication with the client terminals 30 by using the new client key K_(i).

When the client keys K_(i) are seeds for generating the encryption keys EK_(i), the in-server converter 74 generates a new encryption key EK_(i) on the basis of the newly generated client key K_(i) and the existing conversion function Fδ_(i). In this manner, the server 40 can conduct encrypted communication with the client terminals 30 by using the new encryption keys EK_(i).

When the client keys K_(i) are seeds for generating the encryption keys EK_(i), the server 40 may use a combined function CEKGen(K_(S), i) obtained by combining the client key function CKeyGen(K_(S), i) and the conversion function Fδ_(i). In this case, the in-server storage unit 71 stores the combined function CEKGen(K_(S), i) instead of the client key function CKeyGen(K_(S), i) and the conversion function Fδ_(i). The in-server client key generator 73 then generates a new encryption key EK_(i) on the basis of an index i, the existing combined function CEKGen(K_(S), i) stored by the in-server storage unit 71 and the new server key K_(S).

When the client keys K_(i) are seeds for generating the encryption keys EK_(i), the update unit 60 may generate a new encryption key EK_(i) instead of the new client key K_(i) resulting from the update and transmit the new encryption key EK_(i) to the client terminal 30. In this case, the in-client update unit 67 replaces the encryption key EK_(i) stored in the in-client storage unit 61 with the acquired new encryption key EK_(i).

According to the update unit 60 according to the second example, the client key K_(i) or the encryption key EK_(i) can be updated by updating part of the server key K_(S).

FIG. 19 is a schematic diagram of the configuration of the update unit 60 with a client terminal 30 and the server 40 according to a third example. In description of the third example, components having substantially the same configuration and functions as those in the second example will be designated by the same reference numerals and the description thereof will not be repeated except for differences.

In the third example, a client key function CKeyGen(K_(S), i) includes multiple different functions being associated with multiple client keys K_(i), respectively. For example, the client key function CKeyGen(K_(S), i) is composed of multiple functions being associated with multiple client keys K_(i), respectively. For example, the client key function CKeyGen(K_(S), i) contains multiple partial functions corresponding to the third data conversion Fγ for converting a partial sequence of the client key K₁ to be updated into the client key K₁ illustrated in FIG. 12. Thus, with the client key function CKeyGen(K_(S), i), the client key K_(i) generated in association with a specified index i is changed by changing the function part associated with the specified index i.

The generating device 20 outputs a master function Gf (g_(i), i) together with the server key K_(S). In the third example, the master function Gf(g_(i), i) is a function for generating a function part of the client key function CKeyGen(K_(S), i) corresponding to a specified index i from the master key g_(i) and the index i. In other words, when the master key g_(i) and an index i are input to the master function Gf(g_(i), i), a function part corresponding to the index i contained in the client key function CKeyGen(K_(S), i) is generated.

In the third example, the update unit 60 updates the client keys K_(i) to be updated. In addition, the update unit 60 updates master key g_(i) to update a function part corresponding to the client key K_(i) to be updated contained in the client key function CKeyGen(K_(S), i).

In the client key function CKeyGen(K_(S), i), when the third data conversion Fγ is different for each client in the conversion illustrated in FIG. 12, the third data conversion Fγ is the function part corresponding to the index i. The third data conversion Fγ corresponding to the index i will be referred to as Fγ_(i).

The master function Gf(g_(i), i) outputs the third data conversion Fγ as in the following example, for example. Note that the update information generator 82 may generate the third data conversion Fγ on the basis of information such as a system management number and a revision number in addition to the master key g_(i). Here, information other than the master key g_(i) will be referred to as management information w. The management information w may be either secret information or public information. In this case, the master function Gf(g_(i), i, w) outputs the third data conversion Fγ.

For example, the third data conversion Fγ may be a function that outputs an arithmetic sum, an arithmetic product, or an exclusive OR of the client key K_(i)′ before conversion and the master key g_(i) as indicated by Expressions (70) to (72) below. Expression (72) is an expression when K_(i)′ and g_(i) have the same bit length.

Fδ _(i)(K _(i)′)=K _(i) ′+g _(i)  (70)

Fδ _(i)(K _(i)′)=K _(i) ′×g _(i)  (71)

Fδ _(i)(K _(i)′)=K _(i) ′⊕g _(i)  (72)

For another example, the third data conversion Fγ_(i) may be a function that outputs a result of operation on the client key K_(i)′ before conversion, the master key g_(i), and the management information w as indicated by Expression (73) below.

Fγ _(i)(K _(i)′)=K _(i) ′∘g _(i) ∘w  (73)

For another example, the third data conversion Fγ_(i) may be a function that outputs a sequence obtained by converting the sum, the product, or the exclusive OR of the client key K_(i)′ before conversion, the master key g_(i), and the management information w with a function F₁₂ as indicated by Expression (74) below. As an example, F₁₂ is a one-to-one function, a pseudo-random function, or a hash function. F₁₂ outputs l_(i) bits for an input of l_(i) bits.

Fγ _(i)(K _(i)′)=F ₁₂(K _(i) ′∘g _(i) ∘w)  (74)

For another example, the third data conversion Fγ_(i) may assume K_(i)′ as a row vector and multiply K_(i)′ by an invertible matrix g_(i) from the right as indicated by Expression (75) below. For example, the third data conversion Fγ_(i) performs the calculation assuming one bit of K_(i) as an element of a vector and a row vector of 1×l_(i), and g_(i) as an invertible matrix l_(i)×l₁. Alternatively, for example, the third data conversion Fγ_(i) may perform calculation assuming that a number represented by a plurality of bits in K_(i)′ as an element of a vector.

Fγ _(i)(K _(i)′)=K _(i) ′×g _(i)  (75)

For another example, the third data conversion Fγ_(i) may assume K_(i)′ as a column vector and add the product of a matrix w and the column vector g_(i) as indicated by Expression (76) below. For example, the third data conversion Fγ₁ performs the calculation assuming one bit of K_(i)′ as an element of a vector and a column vector of l_(i)×1, w as a matrix of l_(i)×l_(g), and g_(i) as a column vector of l_(g)×1. Alternatively, for example, the third data conversion Fγ_(i) may perform calculation assuming that a number represented by a plurality of bits in K_(i)′, g_(i), and w as an element of a vector.

Fγ _(i)(K _(i)′)=K _(i) ′+w×g _(i)  (76)

For another example, the third data conversion Fγ_(i) may output a result of operation of a sequence obtained by converting the client key K_(i) with a function F₁₂ and a sequence obtained by converting the master key g_(i) by a function F₁₃, as indicated by Expression (77) below. As an example, F₁₃ is a one-to-one function, a pseudo-random function, or a hash function.

Fγ _(i)(K _(i)′)=F ₁₂(K _(i)′)∘F ₁₃(g _(i))  (77)

The third data function Fγ_(i) is not limited to such functions, but may be any function for converting the client key K_(i)′ before conversion with the master key g_(i), the management information w, or the like, into the client key K_(i).

Consider a case in which the client key function CKeyGen(K_(S), i) assumes that an output of a function H(i) represents a bit position in K_(S) and generates a client key by concatenating bits at such positions in K. The function H is a hash function, a pseudo random function, or the like. In this case, the master function Gf(g_(i), i, w) outputs a function H(i∘g_(i)∘w).

The update unit 60 includes an input unit 80, a random number generator 81, a first update information generator 84, a second update information generator 85, and an output unit 83 as illustrated in FIG. 19.

The first update information generator 84 includes a master key generator 95. The master key generator 95 generates a master key g_(i) on the basis of a random number generated by the random number generator 81.

The second update information generator 85 includes a function generator 96, and a client key generator 94. The function generator 96 stores a master function Gf(g_(i), i), and generates a function part corresponding to an index i input by the input unit 80 contained in the client key function CKeyGen(K_(S), i) on the basis of the index i input by the input unit 80 and a master key g_(i) generated by the master key generator 95. The function generator 96 then replaces the part of the existing client key function CKeyGen(K_(S), i) corresponding to the index i input by the input unit 80 with a new function to generate a new client key function CKeyGen(K_(S), i).

The client key generator 94 generates a new client key K_(i) on the basis of the index i input by the input unit 80, the new client key function CKeyGen(K_(S), i) generated by the function generator 96 and the existing server key K_(S).

The output unit 83 outputs the master key g_(i) generated by the first update information generator 84 and the index i input by the input unit 80 as server key update information sri to the server 40. The output unit 83 also outputs, for each of the client terminals 30 storing the client keys K_(i) to be updated, the new client key K_(i) generated by the second update information generator 85 as the client key update information cri.

In the third example, when the client keys K_(i) are seeds for generating the encryption keys EK_(i), the master function Gf(g_(i), i) may generate a conversion function Fδ_(i) associated with a specified index from the master key g_(i) and the index i. In this case, the function generator 96 generates a new conversion function Fδ_(i) on the basis of the index i and the master key g_(i). In this case, the client key generator 94 generates a new encryption key EK_(i) on the basis of the index input by the input unit 80, the new conversion function Fδ_(i) generated by the function generator 96, the existing client key function CKeyGen(K_(S), i) and the existing server key K_(S). The output unit 83 then outputs the new encryption key EK_(i) as client key update information cri. The output unit 83 may also output the client key K_(i) and the conversion function Fδ_(i) as the client key update information cri.

Alternatively, in the third example, when the client keys K_(i) are seeds for generating the encryption keys EK_(i), the function generator 96 may generate a combined function CEKGen(K_(S), i) obtained by combining the new client key function CKeyGen(K_(S), i) and the existing conversion function Fδ_(i) or a combined function CEKGen(K_(S), i) obtained by combining the existing client key function CKeyGen(K_(S), i) and the new conversion function Fδ_(i). The output unit 83 may transmit the combined function CEKGen(K_(S), i) as the server key update information sri to the server 40. In this case, the client key generator 94 generates a new encryption key EK_(i) on the basis of the index i input by the input unit 80, the combined function CEKGen(K_(S), i), and the existing server key K_(S). In this case, the output unit 83 then outputs the new encryption key EK_(i) as the client key update information cri.

FIG. 20 is a flowchart of a process performed by the update unit 60 according to the third example. To begin with, at Step S131, the input unit 80 in the update unit 60 receives as input a set of indices i for specifying the client keys K_(i) to be updated.

Subsequently, at Step S132, the first update information generator 84 generates a master key g_(i) on the basis of a random number. Subsequently, at Step S133, the second update information generator 85 generates a new client key function CKeyGen(K_(S), i) on the basis of the master key g_(i).

Subsequently, at Step S134, the second update information generator 85 generates a new client key K_(i) on the basis of the index i input by the input unit 80, the existing server key K_(S), and the new client key function CKeyGen(K_(S), i).

At Step S135, the output unit 83 then outputs the master key g_(i) and the index i to the server 40. The output unit 83 also outputs, for each of the client terminals 30 storing the client keys K_(i) to be updated, the new client key K_(i).

FIG. 21 is a schematic diagram of partial configurations of a client terminal 30 and the server 40 with the update unit 60 according to the third example. In the third example, the in-client update unit 67 in the client terminal 30 to be updated acquires a client key K_(i) from the update unit 60. The in-client update unit 67 then replaces the client key K_(i) stored in the in-client storage unit 61 with the acquired new client key K_(i). In this manner, the client terminal 30 can conduct encrypted communication with the server 40 by using the new client key K_(i) stored in the in-client storage unit 61 in encryption and decryption.

In the third example, when the client keys K_(i) are seeds for generating the encryption keys EK_(i), the in-client converter 62 generates a new encryption key EK_(i) on the basis of the new client key K_(i) stored by the in-client storage unit 61 and the existing conversion function Fδ_(i). In this manner, the client terminal 30 can conduct encrypted communication with the server 40 by using the new encryption key EK_(i).

In the third example, when the client keys K_(i) are seeds for generating the encryption keys EK_(i), the in-client update unit 67 may acquire a new encryption key EK_(i) instead of the new client key K_(i) resulting from the update from the update unit 60. In this case, the in-client update unit 67 replaces the encryption key EK_(i) stored in the in-client storage unit 61 with the acquired new encryption key EK_(i).

In the third example, the in-server update unit 78 in the server 40 acquires an index i and the master key g_(i) from the update unit 60. The in-server update unit 78 inputs the acquired master key g_(i) and index i to the master function Gf(g_(i), i) stored in advance to generate a function part corresponding to the index i input by the input unit 80 contained in the client key function CKeyGen(K_(S), i). The function part corresponds to the function part to be updated by the update unit 60. The in-server update unit 78 then replaces the part of the existing client key function CKeyGen(K₁, i) corresponding to the index i input by the input unit 80 with a new function to generate a new client key function CKeyGen(K_(S), i). The in-server update unit 78 then replaces the existing client key function CKeyGen(K_(S), i) stored in the in-server storage unit 71 with the new client key function CKeyGen (K_(S), i).

In encryption and decryption, the in-server client key generator 73 generates a new client key K_(i) on the basis of an index i, the new client key function CKeyGen(K_(S), i) stored by the in-server storage unit 71, and the existing server key K_(S). In this manner, the server 40 can conduct encrypted communication with the client terminals 30 by using the new client key K_(i).

In the third example, when the client keys K_(i) are seeds for generating the encryption keys EK_(i) and the master function Gf(g_(i), i) is a function for generating a conversion function Fδ_(i), the in-server update unit 78 generates a new conversion function Fδ_(i) on the basis of the master key g_(i). In this case, the in-server converter 74 generates a new encryption key EK_(i) on the basis of the existing client key K_(i) and the new conversion function Fδ_(i). In this manner, the server 40 can conduct encrypted communication with the client terminals 30 by using the new encryption keys EK_(i).

Alternatively, in the third example, when the client keys K_(i) are seeds for generating the encryption keys EK_(i), the in-server update unit 78 may generate a new combined function CEKGen(K_(S), i) obtained by combining the new client key function CKeyGen(K_(S), i) and the existing conversion function Fδ_(i) or a new combined function CEKGen(K_(S), i) obtained by combining the existing client key function CKeyGen(K_(S), i) and the new conversion function Fδ_(i). The in-server update unit 78 may acquire the combined function CEKGen(K_(S), i) from the generating device 20. In this case, the in-server update unit 78 replaces the combined function CEKGen(K_(S), i) stored in the in-server storage unit 71 with the new combined function CEKGen(K_(S), i). In encryption and decryption, the in-server client key generator 73 then generates a new encryption key EK_(i) on the basis of an index i, the new combined function CEKGen(K_(S), i) stored by the in-server storage unit 71, and the existing server key K_(S). In this manner, the server 40 can conduct encrypted communication with the client terminals 30 by using the new encryption keys EK_(i).

According to the update unit 60 according to the third example, the client key K_(i) or the encryption key EK_(i) can be updated by updating the client key function CKeyGen(K_(S), i) by using the master key g_(i).

FIG. 22 is a schematic diagram of the configuration of the update unit 60 with a client terminal 30 and the server 40 according to a fourth example. In description of the fourth example, components having substantially the same configuration and functions as those in the third example will be designated by the same reference numerals and the description thereof will not be repeated except for differences.

In the fourth example, the update unit 60 updates the client keys K_(i) to be updated. In addition, the update unit 60 generates a new client key function CKeyGen(K_(S), i) to update the client key function CKeyGen(K_(S), i) stored by the server 40.

The update unit 60 includes an input unit 80, a random number generator 81, a first update information generator 84, a second update information generator 85, and an output unit 83 as illustrated in FIG. 22.

The first update information generator 84 includes a master key generator 95 and a function generator 96. The second update information generator 85 includes a client key generator 94.

The output unit 83 outputs the new client key function CKeyGen(K_(S), i) generated by the first update information generator 84 as server key update information sri to the server 40. The output unit 83 also outputs, for each of the client terminals 30 storing the client keys K_(i) to be updated, the new client key K_(i) generated by the second update information generator 85 as the client key update information cri.

In the fourth example, when the client keys K_(i) are seeds for generating the encryption keys EK_(i), the master function Gf(g_(i), i) may generate a conversion function Fδ_(i) associated with a specified index from the master key g_(i) and the index i. In this case, the function generator 96 generates a new conversion function Fδ_(i) on the basis of the index i and the master key g_(i). The output unit 83 then outputs the new conversion function Fδ_(i) instead of the client key function CKeyGen(K_(S), i) as server key update information sri to the server 40.

FIG. 23 is a flowchart of a process performed by the update unit 60 according to the fourth example. To begin with, at Step S141, the input unit 80 in the update unit 60 receives as input a set of indices i for specifying the client keys K_(i) to be updated.

Subsequently, at Step S142, the first update information generator 84 generates a master key g_(i) on the basis of a random number. Subsequently, at Step S143, the first update information generator 84 generates a new client key function CKeyGen(K_(S), i) on the basis of the master key g_(i).

Subsequently, at Step S144, the second update information generator 85 generates a new client key K_(i) on the basis of the index i input by the input unit 80, the existing server key K_(S), and the new client key function CKeyGen(K_(S), i).

At Step S145, the output unit 83 then outputs the client key function CKeyGen(K_(S), i) to the server 40. The output unit 83 also outputs, for each of the client terminals 30 storing the client keys K_(i) to be updated, the new client key K_(i).

FIG. 24 is a schematic diagram of partial configurations of a client terminal 30 and the server 40 with the update unit 60 according to the fourth example.

In the fourth example, the in-server update unit 78 in the server 40 acquires the new client key function CKeyGen(K_(S), i) from the update unit 60. The in-server update unit 78 replaces the existing client key function CKeyGen(K_(S), i) stored in the in-server storage unit 71 with the acquired new client key function CKeyGen(K_(S), i).

In encryption and decryption, the in-server client key generator 73 generates a new client key K_(i) on the basis of an index i, the new client key function CKeyGen(K_(S), i) stored by the in-server storage unit 71, and the existing server key K_(S). In this manner, the server 40 can conduct encrypted communication with the client terminals 30 by using the new client key K_(i).

In the fourth example, when the client keys K_(i) are seeds for generating the encryption keys EK_(i) and the master function Gf(g_(i), i) is a function for generating a conversion function Fδ_(i), the in-server update unit 78 acquires a new conversion function Fδ_(i) instead of the client key function CKeyGen(K_(S), i) from the update unit 60. The in-server update unit 78 then replaces the existing conversion function Fδ_(i) stored in the in-server storage unit 71 with the acquired new conversion function Fδ_(i). In this case, in encryption and decryption, the in-server client key generator 73 generates a client key K_(i) on the basis of an index i, the existing client key function CKeyGen(K_(S), i) and the existing server key K_(S) stored in the in-server storage unit 71. The in-server converter 74 generates a new encryption key EK_(i) on the basis of the generated client key K_(i) and the new conversion function Fδ_(i) stored by the in-server storage unit 71. In this manner, the server 40 can conduct encrypted communication with the client terminals 30 by using the new encryption keys EK_(i).

Alternatively, in the fourth example, when the client keys K_(i) are seeds for generating the encryption keys EK_(i), the in-server update unit 78 may acquire a new combined function CEKGen(K_(S), i) obtained by combining the new client key function CKeyGen(K_(S), i) and the existing conversion function Fδ_(i) or a new combined function CEKGen(K_(S), i) obtained by combining the existing client key function CKeyGen(K_(S), i) and the new conversion function Fδ_(i) from the update unit 60. In this case, the in-server update unit 78 replaces the combined function CEKGen(K_(S), i) stored in the in-server storage unit 71 with the acquired new combined function CEKGen(K_(S), i). In encryption and decryption, the in-server client key generator 73 then generates a new encryption key EK_(i) on the basis of an index i, the new combined function CEKGen(K_(S), i) stored by the in-server storage unit 71, and the existing server key K_(S). In this manner, the server 40 can conduct encrypted communication with the client terminals 30 by using the new encryption keys EK_(i).

According to the update unit 60 according to the fourth example, the client key K_(i) or the encryption key EK_(i) can be updated by updating the client key function CKeyGen(K_(S), i) stored by the server 40.

FIG. 25 is a schematic diagram of the configuration of the update unit 60 with a client terminal 30 and the server 40 according to a fifth example. In description of the fifth example, components having substantially the same configuration and functions as those in the fourth example will be designated by the same reference numerals and the description thereof will not be repeated except for differences.

In the fifth example, a client key function CKeyGen(K_(S), g_(i), i) generates a client key K_(i) specified by an index i on the basis of the index i, a server key K_(S), and a master key g_(i). In other words, the client key function CKeyGen(K_(S), g_(i), i) according to the fifth example additionally uses the master key g_(i) as an argument.

In the fifth example, the client key function CKeyGen(K_(S), g_(i), i) contains the second data conversion Fβ and the third data conversion Fγ illustrated in FIG. 12. In this case, the third data conversion is Fγ_(i)(K_(i)′, g_(i)) using the client key K_(i)′ before conversion and the master key g_(i) as arguments. Alternatively, in the fifth example, the client key function may be CKeyGen(K_(S), g_(i), i, w) and generate a client key K_(i) specified by an index i on the basis of the index i, a server key K_(S), a master key g_(i) and management information w. In this case, the third data conversion may be Fγ_(i)(K_(i)′, g_(i), w) and generate a converted client key K_(i) on the basis of the client key K_(i)′ before conversion, the master key g_(i), and the management information w.

For example, the third data conversion Fγ may be a function that outputs an arithmetic sum, an arithmetic product, or an exclusive OR of the client key K_(i)′ before conversion and the master key g_(i) as indicated by Expressions (80) to (82) below. Expression (82) is an expression when K_(i)′ and g_(i) have the same bit length.

Fδ _(i)(K _(i) ′,g _(i))=K _(i) ′+g _(i)  (80)

Fδ _(i)(K _(i) ′,g _(i))=K _(i) ′×g _(i)  (81)

Fδ _(i)(K _(i) ′,g _(i))=K _(i) ′⊕g _(i)  (82)

For another example, the third data conversion Fγ_(i) may be a function that outputs a result of operation on the client key K_(i)′ before conversion, the master key g_(i), and the management information w as indicated by Expression (83) below.

Fγ _(i)(K _(i) ′,g _(i) ,w)=K _(i) ′∘g _(i) ∘w  (83)

For another example, the third data conversion Fγ_(i) may be a function that outputs a sequence obtained by converting the sum, the product, or the exclusive OR of the client key K_(i)′ before conversion, the master key g_(i), and the management information w with a function F₁₂ as indicated by Expression (84) below. As an example, F₁₂ is a one-to-one function, a pseudo-random function, or a hash function. F₁₂ outputs l_(i) bits for an input of l_(i) bits.

Fδ _(i)(K _(i) ′,g _(i) ,w)=F ₁₂(K _(i) ′∘g _(i) ∘w)  (84)

For another example, the third data conversion Fγ_(i) may assume K_(i)′ as a row vector and multiply K_(i)′ by an invertible matrix g_(i) from the right as indicated by Expression (85) below. For example, the third data conversion Fγ_(i) performs the calculation assuming one bit of K_(i) as an element of a vector and a row vector of 1×l_(i), and g_(i) as an invertible matrix l_(i)×l_(i). Alternatively, for example, the third data conversion Fγ_(i) may perform calculation assuming that a number represented by a plurality of bits in K_(i)′ as an element of a vector.

Fδ _(i)(K _(i) ′,g _(i))=K _(i) ′×g _(i)  (85)

For another example, the third data conversion Fγ_(i) may assume K_(i)′ as a column vector and add the product of a matrix w and the column vector g_(i) as indicated by Expression (86) below. For example, the third data conversion Fγ_(i), performs the calculation assuming one bit of K_(i)′ as an element of a vector and a column vector of l_(i)×1, w as a matrix of l_(i)×l_(g), and g_(i) as a column vector of l_(g)×1. Alternatively, for example, the third data conversion Fγ_(i) may perform calculation assuming that a number represented by a plurality of bits in K_(i)′, g_(i), and w as an element of a vector.

Fγ _(i)(K _(i) ′,g _(i) ,w)=K _(i) ′+w×g _(i)  (86)

For another example, the third data conversion Fγ_(i) may output a result of operation of a sequence obtained by converting the client key K_(i) with a function F₁₂ and a sequence obtained by converting the master key g_(i) by a function F₁₃, as indicated by Expression (87) below. As an example, F₁₃ is a one-to-one function, a pseudo-random function, or a hash function.

Fγ _(i)(K _(i) ′,g _(i))=F ₁₂(K _(i)′)∘F ₁₃(g _(i))  (87)

The third data function Fγ_(i) is not limited to such functions, but may be any function for converting the client key K_(i)′ before conversion with the master key g_(i), the management information w, or the like, into the client key K_(i).

Consider a case in which the client key function CKeyGen(K_(S), i, g_(i)) assumes that an output of a function H(i) represents a bit position in K_(S) and generates a client key by concatenating bits at such positions in K_(S). The function H is a hash function, a pseudo random function, or the like. A function H(i∘g_(i)) in the client key function CKeyGen(K_(S), i, g_(i)) outputs bit positions in the server key K_(S) on the basis of the index i and the master key g_(i). The function H(i∘g_(i)∘w) in the client key function CKeyGen(K_(S), i, g_(i), w) may output bit positions in the server key K_(S) on the basis of the index i, the master key g_(i), and the management information w.

In the fifth example, the update unit 60 then updates the client key K_(i) to be updated and updates the master key g_(i) to update the client key K_(i) to be updated.

The update unit 60 includes an input unit 80, a random number generator 81, a first update information generator 84, a second update information generator 85, and an output unit 83 as illustrated in FIG. 25.

The first update information generator 84 includes a master key generator 95. The master key generator 95 generates a new master key g_(i) on the basis of a random number generated by the random number generator 81.

The second update information generator 85 includes a client key generator 94. The client key generator 94 generates a new client key K_(i) on the basis of the index i input by the input unit 80, the existing client key function CKeyGen(K_(S), g_(i), i), the new master key g_(i), and the existing server key K_(S).

The output unit 83 outputs the new master key g_(i) generated by the first update information generator 84 as server key update information sri to the server 40. The output unit 83 also outputs, for each of the client terminals 30 storing the client keys K_(i) to be updated, the new client key K_(i) generated by the second update information generator 85 as the client key update information cri.

In the fifth example, when the client keys K_(i) are seeds for generating the encryption keys EK_(i), the client key generator 94 may store a combined function CEKGen(K_(S), g_(i), i) obtained by combining the client key function CKeyGen(K_(S), g_(i), i) and the conversion function Fδ_(i). In this case, the client key generator 94 generates a new encryption key EK_(i) on the basis of the index i input by the input unit 80, the combined function CEKGen(K_(S), g_(i), i), the new master key g_(i) and the existing server key K_(S). In this case, the output unit 83 then outputs the new encryption key EK_(i) as the client key update information cri.

FIG. 26 is a flowchart of a process performed by the update unit 60 according to the fifth example. To begin with, at Step S151, the input unit 80 in the update unit 60 receives as input a set of indices i for specifying the client keys K_(i) to be updated.

Subsequently, at Step S152, the first update information generator 84 generates a master key g_(i) on the basis of a random number. Subsequently, at Step S153, the second update information generator 85 generates a new client key K_(i) on the basis of the index i input by the input unit 80, the existing server key K_(S), the new master key g_(i), and the existing client key function CKeyGen(K_(S), g_(i), i).

At Step S154, the output unit 83 then outputs the master key g_(i) to the server 40. The output unit 83 also outputs, for each of the client terminals 30 storing the client keys K_(i) to be updated, the new client key K_(i).

FIG. 27 is a schematic diagram of partial configurations of a client terminal 30 and the server 40 with the update unit 60 according to the fifth example. In the fifth example, the in-server update unit 78 in the server 40 acquires the master key g_(i). The in-server update unit 78 replaces the existing master key g_(i) stored in the in-server storage unit 71 with the acquired new master key g_(i).

In encryption and decryption, the in-server client key generator 73 generates a new client key K_(i) on the basis of an index i, the new master key g_(i) stored in the in-server storage unit 71, the existing client key function CKeyGen(K_(S), g_(i), i) and the existing server key K_(S) stored in the in-server storage unit 71. In this manner, the server 40 can conduct encrypted communication with the client terminals 30 by using the new client key K_(i).

In the fifth example, when the client keys K_(i) are seeds for generating the encryption keys EK_(i), the in-server storage unit 71 may store a new combined function CEKGen(K_(S), g_(i), i) obtained by combining the client key function CKeyGen(K_(S), g_(i), i) and the conversion function Fδ_(i). In this case, in encryption and decryption, the in-server client key generator 73 generates a new encryption key EK_(i) on the basis of an index i, the new master key g_(i), the combined function CEKGen(K_(S), g_(i), i) stored in the in-server storage unit 71, and the existing server key K_(S). In this manner, the server 40 can conduct encrypted communication with the client terminals 30 by using the new encryption keys EK_(i).

According to the update unit 60 according to the fifth example, the client key K_(i) or the encryption key EK_(i) can be updated by updating the client key function CKeyGen(K_(S), g_(i), i) by using the master key g_(i). The channel over which the generating device 20 transmits the server key update information sri and the client key update information cri is preferably a secure channel but may be a channel that is not secure.

As described above, according to the encryption system 10 according to the first embodiment, some of multiple client keys K_(i) or encryption keys EK_(i) can be easily updated even when part of each of the client keys K_(i) is correlated with other client keys K_(i). Furthermore, when the client keys K_(i) are seeds for generating the encryption keys EK_(i), the client key update information cri contains the client key K_(i), the master key g_(i), or the conversion function Fδ_(i), and encryption keys EK_(i) are not leaked and keys can be safely updated even if any of the client key update information cri is leaked.

Second Embodiment

FIG. 28 is a schematic diagram of the configuration of an encryption system 110 according to a second embodiment. The encryption system 110 includes a generating device 120, a first client terminal 131, a second client terminal 132, a server 140, and a re-encrypting device 150.

The generating device 120 generates a first client key K₁, a second client key K₂, and a master key K_(r). As an example, the generating device 120 generates a client key K₁, a client key K₂, and a master key K_(r) on the basis of a random number generated by a random number generator.

The generating device 120 outputs the first client key K₁ to the first client terminal 131. The generating device 120 outputs the second client key K₂ to the second client terminal 132. The generating device 120 further outputs the first client key K₁, the second client key K₂, and the master key K_(r) to the server 140. The generating device 120 may output a server key K_(S) and a client key rule for generating the first client key K₁ and the second client key K₂ to the server 140 similarly to the generating device 20 of the first embodiment instead of the first client key K₁ and the second client key K₂.

The server 140 acquires the client key K₁, the client key K₂, and the master key K_(r) from the generating device 120. The server 140 generates a first re-encryption key K₁ ^((r)) obtained by encrypting the first client key K₁ with the master key K_(r). The server 140 also generates a second re-encryption key K₂ ^((r)) obtained by encrypting the second client key K₂ with the master key K_(r). The server 140 outputs the first re-encryption key K₁ ^((r)) and the second re-encryption key K₂ ^((r)) to the re-encrypting device 150 in response to a request from the re-encrypting device 150. The generating device 120 and the server 140 may be integrated.

The first client terminal 131 acquires and stores the first client key K₁ from the generating device 120. The first client terminal 131 generates a first ciphertext C₁ (=Enc(k₁, m)) obtained by encrypting a plaintext m with the first client key K₁. The first client terminal 131 outputs the first ciphertext C₁ to the re-encrypting device 150.

The re-encrypting device 150 acquires the first ciphertext C₁ from the first client terminal 131. The re-encrypting device 150 outputs a request to the server 140 in response to the acquisition of the first ciphertext C₁ to acquire the first re-encryption key K₁ ^((r)) and the second re-encryption key K₂ ^((r)).

The re-encrypting device 150 generates a second ciphertext C₂ (=Enc(k₂, m)) obtained by encrypting a plaintext m with the second client key K₂ on the basis of the first ciphertext C₁, the first re-encryption key K₁ ^((r)) and the second re-encryption key K₂ ^((r)). The re-encrypting device 150 then outputs the second ciphertext C₂ to the second client terminal 132.

The second client terminal 132 acquires and stores the second client key K₂ from the generating device 120. The second client terminal 132 acquires the second ciphertext C₂ from the re-encrypting device 150. The second client terminal 132 decrypts the second ciphertext C₂ with the second client key K₂ to generate the plaintext m.

A configuration of the re-encrypting device 150 when exclusive OR operation is used as an encryption process will be described. In this case, the plaintext m, the first client key K₁, the second client key K₂, the master key K_(r), the first re-encryption key K₁ ^((r)), the second re-encryption key K₂ ^((r)) a combined key K_(1,2) ^((r)), the first ciphertext C₁, and the second ciphertext C₂ are all binary data having the same bit length.

FIG. 29 is a schematic diagram illustrating a configuration of the re-encrypting device 150. The re-encrypting device 150 includes a receiver 151, an acquiring unit 152, a combined key generator 153, a re-encrypter 154, and a transmitter 155.

The receiver 151 receives the first ciphertext C₁ obtained by exclusive OR operation of the plaintext m and the first client key K₁ from the first client terminal 131. The acquiring unit 152 acquires the first re-encryption key K₁ ^((r)) obtained by exclusive OR operation of the first client key K₁ and the master key K_(r) from the server 140. The acquiring unit 152 also acquires the second re-encryption key K₂ ^((r)) obtained by exclusive OR operation of the second client key K₂ and the master key K_(r).

The combined key generator 153 generates a combined key K_(1,2) ^((r)) by exclusive OR operation of the first re-encryption key K₁ ^((r)) and the second re-encryption key K₂ ^((r)) obtained by the acquiring unit 152. The re-encrypter 154 generates the second ciphertext C₂ by exclusive OR operation of the first ciphertext C₁ received by the receiver 151 and the combined) key K_(1,2) ^((r)) generated by the combined key generator 153. The transmitter 155 transmits the second ciphertext C₂ generated by the re-encrypter 154 to the second client terminal 132.

FIG. 30 is a flowchart of a process performed by the encryption system 110 according to the second embodiment. For transferring a plaintext m through encrypted communication from the first client terminal 131 to the second client terminal 132, the process of the following Steps S201 to S210 is performed.

First, at Step S201, the first client terminal 131 generates a first ciphertext C₁ obtained by exclusive OR operation of the plaintext m and the first client key K₁ as indicated by Expression (101) below.

C ₁ =K ₁ ⊕m  (101)

Subsequently, at Step S202, the first client terminal 131 outputs the first ciphertext C₁ to the re-encrypting device 150. In this case, the first client terminal 131 also outputs information specifying a destination (second client terminal 132) to the re-encrypting device 150.

Subsequently, at Step S203, the re-encrypting device 150 outputs a request to the server 140 in response to acquisition of the first ciphertext C₁ from the first client terminal 131. In this case, the re-encrypting device 150 also outputs information specifying the source (first client terminal 131) and the destination (second client terminal 132) to the server 140.

Subsequently, at Step S204, the server 140 acquires the first client key K₁ stored in the first client terminal 131 that is the source, the second client key K₂ stored in the second client terminal 132 that is the destination, and the master key K_(r). As an example, the server 140 acquires in advance and stores the first client key K₁, the second client key K₂, and the master key K_(r) from the generating device 120. As an example, the server 140 may acquire the keys from the generating device 120 after receiving a request from the re-encrypting device 150. Alternatively, the server 140 may use a random number generated by a random number generator provided therein as a master key K_(r) instead of acquiring the master key K_(r) from the generating device 120.

Subsequently, at Step S205, the server 140 generates the first re-encryption key K₁ ^((r)) obtained by exclusive OR operation of the first client key K₁ and the master key K_(r) as indicated by Expression (102) below. The server 140 also generates the second re-encryption key K₂ ^((r)) obtained by exclusive OR operation of the second client key K₂ and the master key K_(r) as indicated by Expression (103).

K ₁ ^((r)) =K ₁ ⊕K _(r)  (102)

K ₂ ^((r)) =K ₂ ⊕K _(r)  (103)

Subsequently, at Step S206, the server 140 returns the first re-encryption key K₁ ^((r)) and the second re-encryption key K₂ ^((r)) to the re-encrypting device 150.

Subsequently, at Step S207, the re-encrypting device 150 generates a combined key K_(1,2) ^((r)) by exclusive OR operation of the first re-encryption key K₁ ^((r)) and the second re-encryption key K₂ ^((r)) as indicated by Expression (104) below in response to acquisition of the first re-encryption key K₁ ^((r)) and the second re-encryption key K₂ ^((r)).

K _(1,2) ^((r)) =K ₁ ^((r)) ⊕K ₂ ^((r))  (104)

Subsequently, at Step S208, the re-encrypting device 150 generates the second ciphertext C₂ by exclusive OR operation of the first ciphertext C₁ and the combined key K_(1,2) ^((r)) as indicated by Expression (105) below.

C ₂ =C ₁ ⊕K _(1,2) ^((r))  (105)

Subsequently, at Step S209, the re-encrypting device 150 then outputs the second ciphertext C₂ to the second client terminal 132.

The exclusive OR operation of the second ciphertext C₂ and the first client key K₁ is expressed as in Expression (106) below.

C ₂ ⊕K ₂=(C ₁ ⊕K _(1,2) ^((r)))⊕K ₂  (106)

The first ciphertext C₁ is a value obtained by exclusive OR operation of the first client key K₁ and the plaintext m as indicated by Expression (101). The combined key K_(1,2) ^((r)) is a value obtained by exclusive OR operation of the first client key K₁ and the second client key K₂ as indicated by Expression (107) below.

K _(1,2) ^((r))=(K ₁ ⊕K _(r))⊕(K ₂ ⊕K _(r))=K ₁ ⊕K ₂  (107)

Thus, as a result of substituting Expression (101) and Expression (107) into Expression (106), only the plaintext m remains on the right side.

Thus, at Step S210, the second client terminal 132 generates the plaintext m by exclusive OR operation of the second ciphertext C₂ and the second client key K₂ as indicated by Expression (108) below in response to reception of the second ciphertext C₂. As a result, the second client terminal 132 can acquire the plaintext m transmitted from the first client terminal 131.

m=C ₂ ⊕K ₂  (108)

The re-encrypting device 150 may acquire one or both of the first re-encryption key K₁ ^((r)) and the second re-encryption key K₂ ^((r)) from the server 140. In this case, when the first client key K₁ and the second client key K₂ are updated, the server 140 transmits an updated first re-encryption key K₁ ^((r)) and second re-encryption key K₂ ^((r)) to the re-encrypting device 150. The re-encrypting device 150 may add the updated first re-encryption key K₁ ^((r)) and second re-encryption key K₂ ^((r)) to or write the updated first re-encryption key K₁ ^((r)) and second re-encryption key K₂ ^((r)) over the previous first re-encryption key K₁ ^((r)) and second re-encryption key K₂ ^((r)).

As described above, the re-encrypting device 150 according to the second embodiment can convert a first ciphertext C₁ obtained by encrypting a plaintext m with a first client key K₁ into a second ciphertext C₂ obtained by encrypting the plain text m with a second client key K₂ without knowing the first client key K₁ and the second client key K₂.

FIG. 31 is a schematic diagram of an example of hardware configurations of the generating device 20, the client terminals 30, the server 40, and the re-encrypting device 150. Each of the generating device 20, the client terminals 30, the server 40, and the re-encrypting device 150 includes a controller such as a central processing unit (CPU) 201, storage devices such as a read-only memory (ROM) 202 and a random access memory (RAM) 203, a communication interface (I/F) 204 for connecting to a network and establishing communications, and a bus for connecting these components.

Programs to be executed by the generating device 20, the client terminals 30, the server 40, and the re-encrypting device 150 according to the embodiments are embedded on the ROM 202 or the like in advance and provided therefrom. The programs may alternatively be recorded on a computer readable recording medium such as a compact disk read only memory (CD-ROM), a flexible disk (FD), a compact disk recordable (CD-R), and a digital versatile disk (DVD) in a form of a file that can be installed or executed, and provided as a computer program product.

Alternatively, the programs may be stored on a computer system connected to a network such as the Internet, and provided by being downloaded via the network. Still alternatively, the programs may be provided or distributed through a network such as the Internet.

A program to be executed in the generating device 20 according to the embodiments can make a computer function as the components (the input unit 51, the random number generator 52, the server key generator 53, the client key generator 54, and the output unit 55) of the generating device 20 described above. The whole or part of the input unit 51, the random number generator 52, the server key generator 53, the client key generator 54, and the output unit 55 may be implemented by hardware.

A program to be executed in the client terminals 30 according to the embodiments can make a computer function as the components (the in-client storage unit 61, the in-client converter 62, the in-client encrypter 63, the in-client transmitter 64, the in-client receiver 65, the in-client decrypter 66, and the in-client update unit 67) of the client terminals 30 described above. The whole or part of the in-client storage unit 61, the in-client converter 62, the in-client encrypter 63, the in-client transmitter 64, the in-client receiver 65, the in-client decrypter 66, and the in-client update unit 67 may be implemented by hardware.

A program to be executed in the server 40 according to the embodiments can make a computer function as the components (the in-server storage unit 71, the in-server receiver 72, the in-server client key generator 73, the in-server converter 74, the in-server decrypter 75, the in-server encrypter 76, the in-server transmitter 77, and the in-server update unit 78) of the server 40 described above. The whole or part of the in-server storage unit 71, the in-server receiver 72, the in-server client key generator 73, the in-server converter 74, the in-server decrypter 75, the in-server encrypter 76, the in-server transmitter 77, and the in-server update unit 78 may be implemented by hardware.

A program to be executed in the re-encrypting device 150 according to the embodiments can make a computer function as the components (the receiver 151, the acquiring unit 152, the combined key generator 153, the re-encrypter 154, and the transmitter 155) of the re-encrypting device 150 described above. The whole or part of the receiver 151, the acquiring unit 152, the combined key generator 153, the re-encrypter 154, and the transmitter 155 may be implemented by hardware.

In the computer, the CPU 201 can read out programs from a computer-readable storage medium onto a main storage and execute the programs.

While certain embodiments have been described, these embodiments have been presented by way of example only, and are not intended to limit the scope of the inventions. Indeed, the novel embodiments described herein may be embodied in a variety of other forms; furthermore, various omissions, substitutions and changes in the form of the embodiments described herein may be made without departing from the spirit of the inventions. The accompanying claims and their equivalents are intended to cover such forms or modifications as would fall within the scope and spirit of the inventions. 

What is claimed is:
 1. A generating device comprising: a first key generator configured to generate a first key that is a sequence of bits according to a first key rule for generating the first key on the basis of a random number; a second key generator configured to generate multiple second keys that are sequences of bits partially having correlation with one another according to a second key rule for generating the second keys on the basis of the first key; an output unit configured to output the first key and at least one of the second keys; and an update unit configured to generate update information for updating any one of the second keys by updating a partial sequence of the any one of the second keys, the partial sequence having no correlation with the other second keys not to be updated.
 2. The device according to claim 1, wherein the update unit is configured to generate first update information for updating the second key to be updated output from the output unit, and generate second update information for updating the second key to be updated generated from the first key and the second key rule by updating at least one of the second key rule and the first key output from the output unit.
 3. The device according to claim 2, wherein the second keys are seeds for generating encryption keys, the second key generator is configured to generate, for each of the second keys, a conversion function for converting the second key to an encryption key, the output unit is configured to output the second key and the corresponding conversion function, and the update unit is configured to generate the first update information for updating the second key to be updated or for updating the conversion function corresponding to the second key to be updated.
 4. The device according to claim 2, wherein the update unit is configured to generate the second update information for updating the second key to be updated by updating bits of the first key, the bits being a seed for the second key to be updated but not being any of seeds for the other second keys not to be updated.
 5. The device according to claim 2, wherein the second key rule contains different functions for the respective second keys to be generated, the output unit is configured to output a master function for generating the second key rule from a master key together with the first key, and the update unit is configured to update the master key to generate the second update information for updating the second key to be updated by updating the function corresponding to the second key to be updated contained in the second key rule.
 6. The device according to claim 2, wherein the second key rule contains different functions for the respective second keys to be generated, and the update unit is configured to generate second update information for updating the second key to be updated by updating the function corresponding to the second key to be updated contained in the second key rule.
 7. The device according to claim 2, wherein the second key rule is for generating a second key specified by an index specifying one of the second keys on the basis of the index, the first key, and a master key, and the update unit is configured to generate the second update information for updating the second key to be updated by updating the master key.
 8. A generating method comprising: generating a first key that is a sequence of bits according to a first key rule for generating the first key on the basis of a random number; generating multiple second keys that are sequences of bits partially having correlation with one another according to a second key rule for generating the second keys on the basis of the first key; outputting the first key and at least one of the second keys; and generating update information for updating any one of the second keys by updating a partial sequence of the any one of the second keys, the partial sequence having no correlation with the other second keys not to be updated.
 9. A computer program product comprising a computer-readable medium containing a program executed by a computer, the program causing the computer to execute: generating a first key that is a sequence of bits according to a first key rule for generating the first key on the basis of a random number; generating multiple second keys that are sequences of bits partially having correlation with one another according to a second key rule for generating the second keys on the basis of the first key; outputting the first key and at least one of the second keys; and generating update information for updating any one of the second keys by updating a partial sequence of the any one of the second keys, the partial sequence having no correlation with the other second keys not to be updated.
 10. A re-encrypting device comprising: a receiver configured to receive a first ciphertext obtained by exclusive OR operation of a plaintext and a first client key from a first client terminal; an acquiring unit configured to acquire a first re-encryption key obtained by exclusive OR operation of the first client key and a master key, and a second re-encryption key obtained by exclusive OR operation of a second client key stored in a second client terminal and the master key; a combined key generator configured to generate a combined key obtained by exclusive OR operation of the first re-encryption key and the second re-encryption key; a re-encrypter configured to generate a second ciphertext obtained by exclusive OR operation of the first ciphertext and the combined key; and a transmitter configured to transmit the second ciphertext to the second client terminal.
 11. A re-encrypting method comprising: receiving a first ciphertext obtained by exclusive OR operation of a plaintext and a first client key from a first client terminal; acquiring a first re-encryption key obtained by exclusive OR operation of the first client key and a master key, and a second re-encryption key obtained by exclusive OR operation of a second client key stored in a second client terminal and the master key; generating a combined key obtained by exclusive OR operation of the first re-encryption key and the second re-encryption key; generating a second ciphertext obtained by exclusive OR operation of the first ciphertext and the combined key; and transmitting the second ciphertext to the second client terminal.
 12. A computer program product comprising a computer-readable medium containing a program executed by a computer, the program causing the computer to execute: receiving a first ciphertext obtained by exclusive OR operation of a plaintext and a first client key from a first client terminal; acquiring a first re-encryption key obtained by exclusive OR operation of the first client key and a master key, and a second re-encryption key obtained by exclusive OR operation of a second client key stored in a second client terminal and the master key; generating a combined key obtained by exclusive OR operation of the first re-encryption key and the second re-encryption key; generating a second ciphertext obtained by exclusive OR operation of the first ciphertext and the combined key; and transmitting the second ciphertext to the second client terminal. 